CVE-2024-3273

** UNSUPPORTED WHEN ASSIGNED ** A vulnerability, which was classified as critical, was found in D-Link DNS-320L, DNS-325, DNS-327L and DNS-340L up to 20240403. Affected is an unknown function of the file /cgi-bin/nas_sharing.cgi of the component HTTP GET Request Handler. The manipulation of the argument system leads to command injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-259284. NOTE: This vulnerability only affects products that are no longer supported by the maintainer. NOTE: Vendor was contacted early and confirmed immediately that the product is end-of-life. It should be retired and replaced.

CVSS: 7.3Highscored by the publisher (CNA)
Exploited in the wild: Yes, in CISA KEV since 11 Apr 2024CISA deadline for US federal agencies: 2 May 2024unvetted proof-of-concept code on github
EPSS: > 99.9%chance of exploitation in the next 30 daystop 0.1% of scored CVEsFIRST score of 11 Nov 2026
Fix: Patch availablesee the advisories in the references
Published: 4 Apr 2024analysed here 12 Nov 2026

Do first. This vulnerability affects legacy D-Link products. All associated hardware revisions have reached their end-of-life (EOL) or end-of-service (EOS) life cycle and should be retired and replaced per vendor instructions. (CISA's required action for this KEV entry)

Summary

Triage

Attack surface: Server-side
Exploitable: At runtime
Attack vector: network
Weakness: CWE-77 Command Injection

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

Product	Affected versions	Vendor says fixed in
D-Link DNS-320L	20240403Vendor says fixed in: not stated	Not stated by the vendor
D-Link DNS-325	20240403Vendor says fixed in: not stated	Not stated by the vendor
D-Link DNS-327L	20240403Vendor says fixed in: not stated	Not stated by the vendor
D-Link DNS-340L	20240403Vendor says fixed in: not stated	Not stated by the vendor

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

Products named in our analysis

dlink:dns-320l_firmware
dlink:dns-120_firmware
dlink:dnr-202l_firmware
dlink:dns-315l_firmware
dlink:dns-320_firmware
dlink:dns-320lw_firmware
dlink:dns-321_firmware
dlink:dnr-322l_firmware
dlink:dns-323_firmware
dlink:dns-325_firmware
dlink:dns-326_firmware
dlink:dns-327l_firmware
dlink:dnr-326_firmware
dlink:dns-340l_firmware
dlink:dns-343_firmware
dlink:dns-345_firmware
dlink:dns-726-4_firmware
dlink:dns-1100-4_firmware
dlink:dns-1200-05_firmware
dlink:dns-1550-04_firmware

Fix and mitigation

WAF and other mitigations

Can a WAF block it? Partly. The attack is delivered via an HTTP GET request to a specific CGI endpoint with a manipulated system parameter that leads to command injection. Such injection payloads typically contain unusual characters or patterns that a WAF can detect and block without affecting normal users. A WAF rule can match command injection payload in the system parameter of /cgi-bin/nas_sharing.cgi. No tracked WAF vendor has published a rule for this CVE yet, so you would write it yourself.

What a custom rule would match: command injection payload in the system parameter of /cgi-bin/nas_sharing.cgi

Also consider: patch · custom WAF rule · input validation · RASP

Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog: Listed since 11 Apr 2024.
CISA due date: 2 May 2024, the remediation deadline for US federal agencies
CISA required action: This vulnerability affects legacy D-Link products. All associated hardware revisions have reached their end-of-life (EOL) or end-of-service (EOS) life cycle and should be retired and replaced per vendor instructions.
Public exploit code: Unvetted proof-of-concept code on GitHub: 8 GitHub proofs of concept · 1 Nuclei template
CISA SSVC: exploitation active, automatable yes, technical impact totalAssessed by CISA 12 Apr 2024 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

Nuclei

D-Link Network Attached Storage - Command Injection and Backdoor Accountdetection template, critical

GitHub proofs of concept

Chocapikk/CVE-2024-3273100 stars
adhikara13/CVE-2024-327313 stars
Ap0dexMe0/CVE-2024-32735 stars
yarienkiva/honeypot-dlink-CVE-2024-32730 stars

and 4 more repositories

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

Timeline

4 Apr 2024Published
7 Apr 2024First proof-of-concept repository on GitHub (unvetted)3 days later
11 Apr 2024Added to CISA KEV (exploited in the wild)4 days later
12 Apr 2024CISA SSVC assessment: exploitation active1 day later
2 May 2024CISA remediation due date (US federal agencies)20 days later
21 Oct 2025CVE record last updated538 days (about 1 year) later
12 Nov 2026Analysed by vulneraibility.com387 days (about 1 year) later

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Metric	Value	What it means
Attack vector	NetworkReachable over the internet or any routable network.	Reachable over the internet or any routable network.
Attack complexity	LowRepeatable attack, no special conditions.	Repeatable attack, no special conditions.
Privileges required	NoneThe attacker needs no prior access.	The attacker needs no prior access.
User interaction	NoneNo victim action needed.	No victim action needed.
Scope	UnchangedImpact stays within the vulnerable component.	Impact stays within the vulnerable component.
Confidentiality	LowPartial data disclosure.	Partial data disclosure.
Integrity	LowLimited modification possible.	Limited modification possible.
Availability	LowPartial degradation possible.	Partial degradation possible.

Common questions

Is CVE-2024-3273 being exploited?

Yes. CVE-2024-3273 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2024-3273?

CVE-2024-3273 is rated High with a CVSS score of 7.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2024-3273?

Yes. A fix has been recorded for CVE-2024-3273. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2024-3273 affect?

CVE-2024-3273 affects dlink:dns-320l_firmware, dlink:dns-120_firmware, dlink:dnr-202l_firmware, dlink:dns-315l_firmware, and 16 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVD CVE.org CVE Details Source

7 references in the CVE record, grouped by the tags the record gives them.

Advisories (1)

vuldb.com /?submit.304661

Exploits (1)

github.com /netsecfish/dlink

Where the data on this page comes from

CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
NVD: CVSS and CPE data
CISA KEV catalog: exploitation, date added, due date
CISA Vulnrichment (ADP): SSVC decision points
FIRST EPSS: exploit probability and percentile
Nuclei templates: detection templates
PoC-in-GitHub: GitHub repositories that claim a proof of concept

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.