# CVE-2018-20674: Command injection in n/a

> Authenticated attackers can execute arbitrary commands on vulnerable D-Link routers, potentially compromising the device.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jan 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-xh8m-9gqq-4g7c

## What is CVE-2018-20674?

CVE-2018-20674 is a high-severity command injection vulnerability in n/a, published on 9 Jan 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

D-Link DIR-822 C1 before v3.11B01Beta, DIR-822-US C1 before v3.11B01Beta, DIR-850L A* before v1.21B08Beta, DIR-850L B* before v2.22B03Beta, and DIR-880L A* before v1.20B02Beta devices allow authenticated remote command execution.

## Which versions are affected by CVE-2018-20674?

It affects 4 products.


Products: Dlink Dir-822-Us Firmware, Dlink Dir-822 Firmware, Dlink Dir-850l Firmware, Dlink Dir-880l Firmware.

## How do I fix CVE-2018-20674?

No fix has been published for CVE-2018-20674 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-20674 being exploited?

There is no known exploitation of CVE-2018-20674 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2018-20675](https://insights.sbomify.com/CVE-2018-20675/): Auth bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-20674 and fix it if it is affected.

What it is: CVE-2018-20674 is a high-severity command injection vulnerability in n/a, published on 9 Jan 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-20674 in the wild and no public exploit code.

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

## Sources

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

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