# CVE-2019-3421: Command injection in ZX297520V3

> Unauthorized users can exploit a command injection flaw in ZTE ZX297520V3 devices to execute arbitrary commands and control the terminal system.

- **Severity:** High 8.0 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Oct 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-q6g5-8v53-vchj

## What is CVE-2019-3421?

CVE-2019-3421 is a high-severity command injection vulnerability in ZTE Corporation ZX297520V3, published on 31 Oct 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The 7520V3V1.0.0B09P27 version, and all earlier versions of ZTE product ZX297520V3 are impacted by a Command Injection vulnerability. Unauthorized users can exploit this vulnerability to control the user terminal system.

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

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

It affects 1 product.


Products: Ztw Zx297520v3 Firmware.

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

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

## Is CVE-2019-3421 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-3421 is a high-severity command injection vulnerability in ZTE Corporation ZX297520V3, published on 31 Oct 2019. 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-2019-3421 in the wild and no public exploit code.

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

## Sources

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

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