Threats / D-Link / CVE-2024-3273
CVE-2024-3273
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
D-Link Multiple NAS Devices vulnerability
D-Link NAS devices contain a command injection vulnerability (CWE-77) that enables remote code execution when chained with CVE-2024-3272. The flaw affects DNS-320L, DNS-325, DNS-327L, and DNS-340L models.
Verdict
Today item — known-exploited.
Command injection in D-Link NAS appliances permits unauthenticated remote code execution through crafted input. High EPSS score and active exploitation in the wild indicate immediate risk to exposed devices. Patch or isolate affected models urgently.
CISA KEV Yes · 2024-04-115EPSS 0.99997 (verify live)6Exploit Weaponized · public PoC7CVSS 7.33CISA SSVC Exploitation: active · Automatable: yes · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
375 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2024-04-11).
Probability (EPSS)
EPSS 0.99997 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 7.3 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L) · Affected: D-Link, Multiple NAS Devices. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-77 Command Injection — weakness family: Injection.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 7 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a public proof-of-concept / detection template). Catalog entries: nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft malicious input containing shell metacharacters to break out of intended command context.
Business
Attacker gains arbitrary code execution on the NAS device with device privileges.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I chain this vulnerability with CVE-2024-3272 to bypass authentication or initial access controls.
Business
Unauthenticated remote exploitation becomes feasible, eliminating access barriers.
3
Lateral reach — past segmentation narrative 3
Attacker
I execute system commands to establish persistence, exfiltrate data, or pivot to internal networks.
Business
Data stored on NAS is compromised; internal network security perimeter is breached.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05