# CVE-2020-9199: Command injection in B2368-22;B2368-57;B2368-66

> A high-privilege attacker on the LAN can inject commands into Huawei B2368 routers due to insufficient input validation, leading to code execution.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-5jw6-7rrf-x3ww

## What is CVE-2020-9199?

CVE-2020-9199 is a medium-severity command injection vulnerability in B2368-22;B2368-57;B2368-66, published on 3 Sep 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

B2368-22 V100R001C00;B2368-57 V100R001C00;B2368-66 V100R001C00 have a command injection vulnerability. An attacker with high privileges may exploit this vulnerability through some operations on the LAN. Due to insufficient input validation of some parameters, the attacker can exploit this vulnerability to inject commands to the target device.

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

## Which versions are affected by CVE-2020-9199?

It affects 3 products.


Products: Huawei B2368-22 Firmware, Huawei B2368-57 Firmware, Huawei B2368-66 Firmware.

## How do I fix CVE-2020-9199?

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

## Is CVE-2020-9199 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-9199 and fix it if it is affected.

What it is: CVE-2020-9199 is a medium-severity command injection vulnerability in B2368-22;B2368-57;B2368-66, published on 3 Sep 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-9199 in the wild and no public exploit code.

Affected product: B2368-22;B2368-57;B2368-66. 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-2020-9199/ (Markdown: https://insights.sbomify.com/CVE-2020-9199/index.md)
```

## Sources

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

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