# CVE-2019-3419: Denial of service in ZXMP M721 DX

> An attacker can cause a denial of service on the ZTE ZXMP M721 by sending specific packets to the management port.

- **Severity:** Medium 5.7 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/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-vj52-633x-8xpp

## What is CVE-2019-3419?

CVE-2019-3419 is a medium-severity denial of service vulnerability in ZTE Corporation ZXMP M721 DX, 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

A security vulnerability exists in a management port in the version of ZTE's ZXMP M721V3.10P01B10_M2NCP. An attacker could exploit this vulnerability to build a link to the device and send specific packets to cause a denial of service.

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

It affects 1 product.


Products: Zte Zxmp M721 Dx Firmware.

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

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

## Is CVE-2019-3419 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-3419 is a medium-severity denial of service vulnerability in ZTE Corporation ZXMP M721 DX, 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-3419 in the wild and no public exploit code.

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

## Sources

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

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