basicsecurity.net
Proof, not just disclosure.
Threats / D-Link / CVE-2024-3273
CVE-2024-3273 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

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-113EPSS 0.99997 (verify live)4Exploit Weaponized · public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit 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
341 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).
CISA KEV ↗Confirmed
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
Affected: D-Link, Multiple NAS Devices. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-77 Command Injection — weakness family: Injection.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution 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 board
1

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

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • Weaponized exploit available (VulnCheck)
  • 341 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Public exploit availability
  • Catalogued by VulDB (CNA)
  • Named finder/reporter credit (CVE.org)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • Disclosure & credit2
    Catalogued by VulDBCNA