# CVE-2019-12511: Root Command Injection via MAC Address in SOAP API

> Attackers can execute arbitrary root commands via MAC address injection in the SOAP API, requiring QoS enabled and valid authentication.

- **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:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Feb 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-3c2g-95gg-q68p

## What is CVE-2019-12511?

CVE-2019-12511 is a critical command injection vulnerability in n/a, published on 24 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In NETGEAR Nighthawk X10-R9000 prior to 1.0.4.26, an attacker may execute arbitrary system commands as root by sending a specially-crafted MAC address to the "NETGEAR Genie" SOAP endpoint at AdvancedQoS:GetCurrentBandwidthByMAC. Although this requires QoS being enabled, advanced QoS being enabled, and a valid authentication JWT, additional vulnerabilities (CVE-2019-12510) allow an attacker to interact with the entire SOAP API without authentication. Additionally, DNS rebinding techniques may be used to exploit this vulnerability remotely. Exploiting this vulnerability is somewhat involved. The following limitations apply to the payload and must be overcome for successful exploitation: - No more than 17 characters may be used. - At least one colon must be included to prevent mangling. - A single-quote and meta-character must be used to break out of the existing command. - Parent command remnants after the injection point must be dealt with. - The payload must be in all-caps. Despite these limitations, it is still possible to gain access to an interactive root shell via this vulnerability. Since the web server assigns certain HTTP headers to environment variables with all-caps names, it is possible to insert a payload into one such header and reference the subsequent environment variable in the injection point.

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

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

It affects 1 product.


Products: Netgear Nighthawk X10-R9000 Firmware.

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

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

## Is CVE-2019-12511 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-12510](https://insights.sbomify.com/CVE-2019-12510/): Auth Bypass Via X-Forwarded-For Header in SOAP API (critical 9.1)
- [CVE-2019-12512](https://insights.sbomify.com/CVE-2019-12512/): Stored XSS via X-Forwarded-For Header During Incorrect Login (medium 6.1)
- [CVE-2019-12513](https://insights.sbomify.com/CVE-2019-12513/): Stored XSS via DHCP Discover Request Hostname (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-12511 is a critical command injection vulnerability in n/a, published on 24 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-12511 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-2019-12511/ (Markdown: https://insights.sbomify.com/CVE-2019-12511/index.md)
```

## Sources

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

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