What is CVE-2024-3273?

CVE-2024-3273 is D-Link DNS-320L/DNS-325/DNS-327L/DNS-340L HTTP GET Request nas_sharing.cgi command injection. The supplied enrichment data classifies it as Remote Code Exec mapped to CWE-77 Command Injection.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Yes: CISA KEV signal present. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

Is there a public exploit?

62 public PoC repositories reported; 2 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS, EDR process telemetry, host service logs where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2024-3273 using CVSS 9.8, EPSS 100%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

Publicly linked actor or ransomware signals in the supplied enrichment data: Sea Turtle (), Lazarus Group (), APT 22 (). Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Treat as emergency remediation because CISA KEV status is present. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

CISA KEVcriticalRemote Code Execpublic exploit

CVE-2024-3273

CVE-2024-3273 — D-Link DNS-320L/DNS-325/DNS-327L/DNS-340L HTTP GET Request nas_sharing.cgi command injection

Q: Is it in CISA KEV?

Yes. The supplied enrichment data lists CVE-2024-3273 in CISA KEV with 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.. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

** 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.

Published Apr 4, 2024Updated Jun 17, 2026Sources: NVD, D-Link (CNA), CISA, FIRST EPSS, GitHub, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Confirmed

CISA KEV, listed Apr 11, 2024

EPSS

100%

top of FIRST's scoreset

Affects

D-Link

4 products listed

CVSS base

9.8

critical · 4 sources

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

Active

none · proof-of-concept · active

Automatable

Yes

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

The vendor's own words where we have them.

Upgrade DNS-320L to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

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.

Federal deadline May 2, 2024 — passed 869 days ago

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Treat as emergency remediation because CISA KEV status is present.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
D-Link	DNS-320L	20240403	Vulnerable
D-Link	DNS-325	20240403	Vulnerable
D-Link	DNS-327L	20240403	Vulnerable
D-Link	DNS-340L	20240403	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

High

Confidentiality

High

Integrity

High

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

None

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
7.3	CVSS 3.1	high	3.9	3.4	vuldb.com (CNA), D-Link (CNA)
9.8	CVSS 3.1	critical	3.9	5.9	NVD
7.5	CVSS 2.0	high	10	6.4	vuldb.com (CNA), D-Link (CNA)
7.3	CVSS 3.0	high	—	—	D-Link (CNA)

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

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-77 · Improper Neutralization of Special Elements used in a Command ('Command Injection')

Execute Unauthorized Code or Commands

Mitigation: If at all possible, use library calls rather than external processes to recreate the desired functionality.

Weakness & attack patterns

CWE-77Command Injection

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-40 · Manipulating Writeable Terminal DevicesCAPEC-75 · Manipulating Writeable Configuration FilesCAPEC-15 · Command DelimitersCAPEC-136 · LDAP InjectionCAPEC-248 · Command InjectionCAPEC-76 · Manipulating Web Input to File System CallsCAPEC-43 · Exploiting Multiple Input Interpretation LayersCAPEC-183 · IMAP/SMTP Command Injection

CISA KEV details

CISA lists a CVE here once it has evidence of exploitation against real targets.

CISAThat month →

Listed

Apr 11, 2024

Federal deadline

May 2, 2024

passed 869 days ago

Ransomware use

Unknown

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a date to argue against.

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

2 of the 5 sampled are weaponized

Exploit entries

Exploit-DB and CTI exploit indexes

Malware

Families a CTI source ties to this CVE. One named, with the total it tracks.

Families tracked

Named

cobalt_strike

win.cobalt_strike, cobalt_strike, Cobalt Strike

Social mentions

Posts naming this CVE. Attention, not evidence of exploitation — it spikes on disclosure and decays whether or not anything is exploited.

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Search application, proxy, and WAF logs for requests touching /cgi-bin/nas_sharing.cgi.
Prioritize edge telemetry for network-reachable DNS-320L, DNS-325, DNS-327L, DNS-340L.
Monitor for scanner or exploit-pattern traffic after 62 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPSEDR process telemetryhost service logs

Groups associated with this CVE

Groups reported in connection with this vulnerability. A reported association, not a confirmed observation of that group using it — and not scoped to any sector or campaign.

Sea TurtleLazarus GroupAPT 22

hash334e32e7eea638089a7259c594d87db965
SOCRadar Threat Exchange Services · Jul 11, 2026
hashb05579c5144602216ce0787cf1161bb60a67e9e265
SOCRadar Threat Exchange Services · Jul 11, 2026
hash49152:deurfqriidw7kamngrs7qibb8gdcdomsu+zomwghvls3uewtzkcfz6gc7ppyziil:c+vq5pmgcpv+
SOCRadar Threat Exchange Services · Jun 29, 2026

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 9.8 (AV:N)
Jun 17, 2026 · NVD
2025
Bulletin released on NIST.
Jul 31, 2025 · SOCRadar CTI
Bulletin released on NIST.
Jul 30, 2025 · SOCRadar CTI
Bulletin released on NIST.
Jul 30, 2025 · SOCRadar CTI
Bulletin released on Mitre.
Jul 28, 2025 · SOCRadar CTI
2024
Added to CISA KEV catalog
Apr 11, 2024 · CISA
Reported · VulDB entry last update
Apr 11, 2024 · D-Link
Initial · CVE published
Apr 4, 2024 · NVD
Reported · Advisory disclosed
Apr 3, 2024 · D-Link
Reported · VulDB entry created
Apr 3, 2024 · D-Link

Source activity

Readings a source repeats on a schedule, counted rather than listed.

11×TweetsMay 20, 2024 – May 7, 2026 · SOCRadar CTI
10×ModifiedMay 17, 2024 – Oct 30, 2025 · SOCRadar CTI
3×Github ReposSep 21, 2024 – Apr 25, 2026 · SOCRadar CTI
1×SVRS was changedJun 2, 2024 · SOCRadar CTI

References

9 on the record

github.com/netsecfish/dlink
Exploit, Third Party Advisory, NIST
supportannouncement.us.dlink.com/security/publication.aspx?name=SAP10383
Vendor Advisory, NIST
vuldb.com/?ctiid.259284
Permissions Required, VDB Entry, NIST, Mitre
vuldb.com/?id.259284
Third Party Advisory, VDB Entry, NIST, Mitre
vuldb.com/?submit.304661
Third Party Advisory, VDB Entry, NIST, Mitre
www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-3273
US Government Resource
www.greynoise.io/blog/cve-2024-3273-d-link-nas-rce-exploited-in-the-wild
Third Party Advisory, GITHUB, NIST
news.ycombinator.com/item?id=39960107
NIST

Coverage

2 stories from the feeds we poll

Elsewhere on this site

D-Linkevery CVE for this vendor
April 2024what else CISA listed
Remote Code Execsame class
CWE-77other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

Only the 3 indicator(s) reported for this CVE are available; no packet-level or host-forensic artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2024-3273 is D-Link DNS-320L/DNS-325/DNS-327L/DNS-340L HTTP GET Request nas_sharing.cgi command injection, a critical vulnerability affecting DNS-320L, DNS-325, DNS-327L, DNS-340L from D-Link. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 62 public PoC repositories reported; 2 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 9.8 describes technical severity, while EPSS 100% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.