# CVE-2019-3422: Information disclosure in MF910S

> Attackers can reverse-engineer the Telnet password via the upgrade tool to remotely access the device and leak information.

- **Severity:** Medium 6.2 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Nov 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-h5fw-xjj5-9cgr

## What is CVE-2019-3422?

CVE-2019-3422 is a medium-severity vulnerability in ZTE MF910S, published on 7 Nov 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Sec Consult Security Lab reported an information disclosure vulnerability in MF910S product to ZTE PSIRT in October 2019. Through the analysis of related product team, the information disclosure vulnerability is confirmed. The MF910S product's one-click upgrade tool can obtain the Telnet remote login password in the reverse way. If Telnet is opened, the attacker can remotely log in to the device through the cracked password, resulting in information leakage. The MF910S was end of service on October 23, 2019, ZTE recommends users to choose new products for the purpose of better security.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Zte Mf910s Firmware.

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

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

## Is CVE-2019-3422 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-3422 is a medium-severity vulnerability in ZTE MF910S, published on 7 Nov 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-3422 in the wild and no public exploit code.

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

## Sources

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

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