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

> Attackers can execute arbitrary commands on Xiaomi routers via crafted JSON data in the guest Wi-Fi settings feature.

- **Severity:** Critical 9.8 (`CVSS:3.0/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:** 15 Jul 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-4qff-947c-f4j6

## What is CVE-2018-14010?

CVE-2018-14010 is a critical command injection vulnerability in n/a, published on 15 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OS command injection in the guest Wi-Fi settings feature in /cgi-bin/luci on Xiaomi R3P before 2.14.5, R3C before 2.12.15, R3 before 2.22.15, and R3D before 2.26.4 devices allows an attacker to execute any command via crafted JSON data.

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

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

It affects 4 products.


Products: Mi Xiaomi R3, Mi Xiaomi R3c Firmware, Mi Xiaomi R3d Firmware, Mi Xiaomi R3p Firmware.

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

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

## Is CVE-2018-14010 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-14010 is a critical command injection vulnerability in n/a, published on 15 Jul 2018. 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-2018-14010 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-14010/ (Markdown: https://insights.sbomify.com/CVE-2018-14010/index.md)
```

## Sources

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

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