# CVE-2019-20680: Command injection in n/a

> Authenticated attackers can execute arbitrary commands on various NETGEAR routers via command injection vulnerabilities.

- **Severity:** High 7.0 (`CVSS:3.0/AC:L/AV:A/A:L/C:H/I:H/PR:L/S:U/UI:R`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Apr 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-x7mm-6r2x-9w7p

## What is CVE-2019-20680?

CVE-2019-20680 is a high-severity command injection vulnerability in Netgear D7000 Firmware, published on 15 Apr 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Certain NETGEAR devices are affected by command injection by an authenticated user. This affects D7000v2 before 1.0.0.53, R6220 before 1.1.0.80, R6260 before 1.1.0.64, R6700 before 1.0.2.6, R6700v2 before 1.2.0.36, R6800 before 1.2.0.36, R6900 before 1.0.2.4, R6900P before 1.3.1.64, R6900v2 before 1.2.0.36, R7000 before 1.0.9.60, R7000P before 1.3.1.64, R7800 before 1.0.2.60, R7900 before 1.0.3.8, R7900P before 1.4.1.30, R8000 before 1.0.4.46, R8000P before 1.4.1.30, R8300 before 1.0.2.128, R8500 before 1.0.2.128, R8900 before 1.0.4.12, R9000 before 1.0.4.12, and XR500 before 2.3.2.32.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2019-20680?

It affects 19 products.


Products: Netgear D7000 Firmware, Netgear R6220 Firmware, Netgear R6260 Firmware, Netgear R6700 Firmware, Netgear R6800 Firmware, Netgear R6900 Firmware, Netgear R6900p Firmware, Netgear R7000 Firmware, Netgear R7000p Firmware, Netgear R7800 Firmware, Netgear R7900 Firmware, Netgear R7900p Firmware, Netgear R8000 Firmware, Netgear R8000p Firmware, Netgear R8300 Firmware, Netgear R8500 Firmware, Netgear R8900 Firmware, Netgear R9000 Firmware, Netgear Xr500 Firmware.

## How do I fix CVE-2019-20680?

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

## Is CVE-2019-20680 being exploited?

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

## Other vulnerabilities in Netgear D7000 Firmware

- [CVE-2021-45497](https://insights.sbomify.com/CVE-2021-45497/): Auth bypass in n/a (critical 9.4)
- [CVE-2021-45496](https://insights.sbomify.com/CVE-2021-45496/): Auth bypass in n/a (critical 9.1)
- [CVE-2018-21169](https://insights.sbomify.com/CVE-2018-21169/): Misconfiguration in n/a (high 8.8)
- [CVE-2017-18791](https://insights.sbomify.com/CVE-2017-18791/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2021-45512](https://insights.sbomify.com/CVE-2021-45512/): Weak cryptography in n/a (high 8.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-20680 and fix it if it is affected.

What it is: CVE-2019-20680 is a high-severity command injection vulnerability in Netgear D7000 Firmware, published on 15 Apr 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-20680 in the wild and no public exploit code.

Affected product: Netgear D7000 Firmware. 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-2019-20680/ (Markdown: https://insights.sbomify.com/CVE-2019-20680/index.md)
```

## Sources

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

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