Threats / D-Link / CVE-2022-40799
CVE-2022-40799
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
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-054EPSS 0.31719 (verify live)5Exploit Public PoC6CVSS 8.8 (CISA)3CISA SSVC Exploitation: active · Automatable: no · Impact: total3
01
Is it exploitable?
— the evidence, ranked above the scoreExploit 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).
Probability (EPSS)
EPSS 0.31719 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 8.8 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) · Affected: D-Link, DNR-322L. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
Weakness (CWE)
Mapped to CWE-494 Download Without Integrity Check — weakness family: Path traversal / file.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · 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 980 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.
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 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