# CVE-2019-3412: Command injection in ZTE MF920

> Attackers can execute arbitrary commands on ZTE MF920 devices due to inadequate parameter verification in specific interfaces.

- **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:** 11 Jun 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-cf37-hf6f-gwfg

## What is CVE-2019-3412?

CVE-2019-3412 is a critical command injection vulnerability in ZTE MF920, published on 11 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

All versions up to BD_R218V2.4 of ZTE MF920 product are impacted by command execution vulnerability. Due to some interfaces do not adequately verify parameters, an attacker can execute arbitrary commands through specific interfaces.

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

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

It affects 1 product.


Products: Zte Mf920 Firmware.

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

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

## Is CVE-2019-3412 being exploited?

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

## Other vulnerabilities in ZTE MF920

- [CVE-2019-3411](https://insights.sbomify.com/CVE-2019-3411/): Information disclosure in ZTE MF920 (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-3412 is a critical command injection vulnerability in ZTE MF920, published on 11 Jun 2019. 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-3412 in the wild and no public exploit code.

Affected product: ZTE MF920. 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-3412/ (Markdown: https://insights.sbomify.com/CVE-2019-3412/index.md)
```

## Sources

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

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