# CVE-2022-23138: Weak cryptography in MF297D

> Weak random values in ZTE MF297D devices reduce security, potentially allowing attackers to bypass cryptographic protections.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-3gmx-3pqv-qcgj

## What is CVE-2022-23138?

CVE-2022-23138 is a high-severity vulnerability in MF297D, published on 9 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ZTE's MF297D product has cryptographic issues vulnerability. Due to the use of weak random values, the security of the device is reduced, and it may face the risk of attack.

Weakness: CWE-330 (Use of Insufficiently Random Values)

## Which versions are affected by CVE-2022-23138?

It affects 1 product.


Products: Zte Mf297d Firmware.

## How do I fix CVE-2022-23138?

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

## Is CVE-2022-23138 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-23138 and fix it if it is affected.

What it is: CVE-2022-23138 is a high-severity vulnerability in MF297D, published on 9 Jun 2022. 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-2022-23138 in the wild and no public exploit code.

Affected product: MF297D. 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-2022-23138/ (Markdown: https://insights.sbomify.com/CVE-2022-23138/index.md)
```

## Sources

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

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