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

D-Link DNR-322L vulnerability

D-Link DNR-322L contains an integrity check bypass in code download functionality, allowing authenticated attackers to execute arbitrary OS commands.

Verdict

Today item — known-exploited.

Authenticated attackers can exploit missing integrity verification during code downloads to achieve OS-level command execution on affected DNR-322L devices. Products are end-of-life or end-of-service; discontinuation is recommended.

CISA KEV Yes · 2025-08-053EPSS 0.31328 (verify live)4Exploit Public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit available
Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
3 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 2025-08-05).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.31328 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: D-Link, DNR-322L. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-494 Download Without Integrity Check — weakness family: Path traversal / file.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-494 · Download Without Integrity CheckPath traversal / file
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 authenticate to the device using valid credentials.
Business
Legitimate administrative access is a prerequisite for exploitation.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I initiate a code download without the device verifying file integrity or authenticity.
Business
Lack of cryptographic validation creates the attack surface.
3

Lateral reach — past segmentation narrative 3

Attacker
I supply malicious code that the device accepts and executes at OS level.
Business
Complete device compromise enables data theft, lateral movement, and persistent access.
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)
  • Public PoC available (VulnCheck)
  • 3 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Public exploit availability
  • Catalogued by mitre (CNA)
  • 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.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by mitreCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.