# CVE-2021-45382: D-Link Multiple Routers Remote Code Execution

> Attackers can execute arbitrary commands on vulnerable D-Link routers via the DDNS function, but no patch is available as the devices are end-of-life.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 4 Apr 2022 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Feb 2022
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-5wgx-qvpv-2353

## What is CVE-2021-45382?

CVE-2021-45382 is a critical command injection vulnerability in n/a, published on 17 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A Remote Command Execution (RCE) vulnerability exists in all series H/W revisions D-link DIR-810L, DIR-820L/LW, DIR-826L, DIR-830L, and DIR-836L routers via the DDNS function in ncc2 binary file. Note: DIR-810L, DIR-820L, DIR-830L, DIR-826L, DIR-836L, all hardware revisions, have reached their End of Life ("EOL") /End of Service Life ("EOS") Life-Cycle and as such this issue will not be patched.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2021-45382?

It affects 6 products.


Products: Dlink Dir-810l Firmware, Dlink Dir-820l Firmware, Dlink Dir-820lw Firmware, Dlink Dir-826l Firmware, Dlink Dir-830l Firmware, Dlink Dir-836l Firmware.

## How do I fix CVE-2021-45382?

No fix has been published for CVE-2021-45382 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 25 Apr 2022.

## Is CVE-2021-45382 being exploited?

Yes. Attackers have exploited CVE-2021-45382 in the wild since at least 4 Apr 2022.

Public exploit code:

- D-Link - Remote Command Execution (nuclei): http/cves/2021/CVE-2021-45382.yaml

## Other vulnerabilities in n/a

- [CVE-2022-34974](https://insights.sbomify.com/CVE-2022-34974/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-45382 and fix it if it is affected.

What it is: CVE-2021-45382 is a critical command injection vulnerability in n/a, published on 17 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2021-45382 in the wild since at least 4 Apr 2022.

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-2021-45382/ (Markdown: https://insights.sbomify.com/CVE-2021-45382/index.md)
```

## Sources

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

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