CVE-2022-23138
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedZTE'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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe ZTE MF297D device uses weak random values in cryptographic operations, likely in key generation, session tokens, or other security-critical functions. Weak random number generation (insufficient entropy or predictable PRNG) allows attackers to potentially guess or derive cryptographic secrets, compromising confidentiality and authentication mechanisms.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= mf297d_nordic1_b05CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm device model is ZTE MF297DAccess the device web interface or administrative panel and locate the device information page to verify the model number displays as MF297DAffected if The device is not a ZTE MF297D model, then this specific CVE does not apply
-
Identify installed firmware versionIn the device web interface, navigate to Status or Device Information section to view the current firmware version. Alternatively, access the device via console/AT commands and query the firmware versionAffected if Unable to retrieve firmware version information from the device
-
Compare firmware version against affected releaseCompare the installed firmware version string to the affected version: mf297d_nordic1_b05. Exact string match indicates the device contains the vulnerable code with weak random number generation in cryptographic operationsAffected if Installed firmware version exactly matches mf297d_nordic1_b05, indicating the device uses weak random values in crypto functions as described in this CVE
-
Document firmware version for trackingRecord the exact firmware version string found on the device for vulnerability management records and future re-verification after any updatesAffected if This step is informational regardless of version - maintains audit trail
A user is affected if they have a ZTE MF297D device running firmware version mf297d_nordic1_b05, as this specific version contains the weak random number generation in cryptographic operations vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataContact ZTE for a firmware update addressing the weak random value vulnerability. If no patch is available, consider network segmentation or device replacement to reduce risk until a vendor fix is released.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-23138 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-23138 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data