# CVE-2022-40799: D-Link DNR-322L Download of Code Without Integrity Check

> An authenticated attacker can execute OS-level commands on D-Link DNR-322L devices via a data integrity failure in the Backup Config feature.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 5 Aug 2025 (CISA KEV)
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Nov 2022
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-xh8c-gmc9-9v6x

## What is CVE-2022-40799?

CVE-2022-40799 is a high-severity command injection vulnerability in n/a, published on 29 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-494 (Download of Code Without Integrity Check)

## Which versions are affected by CVE-2022-40799?

It affects 1 product.


Products: Dlink Dnr-322l Firmware.

## How do I fix CVE-2022-40799?

No fix has been published for CVE-2022-40799 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 26 Aug 2025.

## Is CVE-2022-40799 being exploited?

Yes. Attackers have exploited CVE-2022-40799 in the wild since at least 5 Aug 2025.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-40799 and fix it if it is affected.

What it is: CVE-2022-40799 is a high-severity command injection vulnerability in n/a, published on 29 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2022-40799 in the wild since at least 5 Aug 2025.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-40799/ (Markdown: https://insights.sbomify.com/CVE-2022-40799/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-40799
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-40799
- OSV: https://osv.dev/vulnerability/CVE-2022-40799

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-40799/
Summaries are generated and may contain mistakes; the official description above is the record.