What is CVE-2022-40799?

CVE-2022-40799 is D-Link DNR-322L Download of Code Without Integrity Check Vulnerability. The supplied enrichment data classifies it as Unclassified mapped to CWE-494 CWE-494.

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?

5 public PoC repositories reported; 0 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 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-2022-40799 using CVSS 8.8, EPSS 32%, 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: Void Rabisu (), RomCom (), APT 28 (), APT 5 (), 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 KEVhighpublic exploit

CVE-2022-40799

CVE-2022-40799 — D-Link DNR-322L Download of Code Without Integrity Check Vulnerability

Q: Is it in CISA KEV?

Yes. The supplied enrichment data lists CVE-2022-40799 in CISA KEV with required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

Data Integrity Failure in 'Backup Config' in D-Link DNR-322L <= 2.60B15 allows an authenticated attacker to execute OS level commands on the device.

Published Nov 29, 2022Updated Jun 17, 2026Sources: NVD, D-Link (CNA), CISA, FIRST EPSS, 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 Aug 5, 2025

EPSS

32%

ahead of 98% of scored CVEs

Affects

D-Link

DNR-322L

CVSS base

8.8

high

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

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 DNR-322L to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

CISA required action

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Federal deadline Aug 26, 2025 — passed 388 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	DNR-322L	—	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

Low

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
8.8	CVSS 3.1	high	2.8	5.9	NVD, CNA

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

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-494 · Download of Code Without Integrity Check

Execute Unauthorized Code or Commands
Alter Execution Logic
Other

Mitigation: Perform proper forward and reverse DNS lookups to detect DNS spoofing.

Weakness & attack patterns

CWE-494

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

CAPEC-187 · Malicious Automated Software UpdateCAPEC-184 · Software Integrity AttackCAPEC-533 · Malicious Manual Software UpdateCAPEC-185 · Malicious Software DownloadCAPEC-186 · Malicious Software Update

T1195.002Supply Chain Compromise: Compromise Software Supply Chain
T1072Software Deployment Tools
T1195.001Supply Chain Compromise: Software Dependencies and Development Tools

CISA KEV details

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

CISAThat month →

Listed

Aug 5, 2025

Federal deadline

Aug 26, 2025

passed 388 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

Exploit entries

Exploit-DB and CTI exploit indexes

Detection

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

Prioritize edge telemetry for network-reachable DNR-322L.
Monitor for scanner or exploit-pattern traffic after 5 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPS

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.

Void RabisuRomComAPT 28APT 5APT 22

1 more threat groups on this CVEShowing 5 of 6 · Attribution, campaigns and the malware each one runsUnlock free

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 8.8 (AV:N)
Jun 17, 2026 · NVD
2025
Bulletin released on NIST.
Aug 7, 2025 · SOCRadar CTI
Cve is exploited D-Link DNR-322L Download of Code Without Integrity Check Vulnerability
Aug 6, 2025 · SOCRadar CTI
Added to CISA KEV catalog
Aug 5, 2025 · CISA
2023
CVE is exploited. "nomi-sec/PoC-in-GitHub"
Dec 7, 2023 · SOCRadar CTI
2022
Initial · CVE published
Nov 29, 2022 · NVD

Source activity

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

21×SVRS was changedMay 13, 2023 – Sep 5, 2025 · SOCRadar CTI
3×TweetsAug 6, 2025 – Aug 20, 2025 · SOCRadar CTI
2×ModifiedApr 26, 2025 – Aug 6, 2025 · SOCRadar CTI

References

4 on the record

gitlab.com/lu-ka/cve-2022-40799
Exploit, Third Party Advisory, NIST, MITRE
www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2022-40799
US Government Resource
www.dlink.com/uk/en/products/dnr-322l-cloud-network-video-recorder
Product, NIST, Vendor Advisory
nvd.nist.gov/vuln/detail/CVE-2022-40799
Vendor Advisory

Coverage

1 story from the feeds we poll

August 2025 CVE Landscape
recordedfuture.com · Sep 15, 2025

Elsewhere on this site

D-Linkevery CVE for this vendor
August 2025what else CISA listed
Unclassifiedsame class
CWE-494other 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.

No confirmed IOCs, IP addresses, domains, file hashes, or malware 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-2022-40799 is D-Link DNR-322L Download of Code Without Integrity Check Vulnerability, a high vulnerability affecting DNR-322L 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: 5 public PoC repositories reported; 0 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 8.8 describes technical severity, while EPSS 32% 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.