CVE-2025-20754
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 · uneditedIn Modem, there is a possible system crash due to an incorrect bounds check. This could lead to remote denial of service, if a UE has connected to a rogue base station controlled by the attacker, with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: MOLY01689251; Issue ID: MSV-4840.
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 · high confidenceA bounds check vulnerability exists in cellular modem firmware that can be triggered when User Equipment (UE) connects to a rogue base station controlled by an attacker. The attacker sends specially crafted data that exploits the incorrect bounds check, causing the modem to crash and resulting in denial of service. No user interaction or elevated privileges are required for exploitation.
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 dataall versionsall versionsall versionsall versionsCVSS 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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
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.
-
Identify the cellular modem modelCheck the device documentation, system information, or AT command output (e.g., AT+CGMM) to determine if the modem is Mediatek Nr15, Nr16, Nr17, or Nr17rAffected if The modem model is one of Mediatek Nr15, Nr16, Nr17, or Nr17r, as all versions of these are affected
-
Check the firmware versionQuery the modem firmware version using AT commands (e.g., AT+CGMR) or through the device management interfaceAffected if The modem is a Mediatek Nr15, Nr16, Nr17, or Nr17r and the firmware version is known - compare against the patched version MOLY01689251 to determine if the patch has been applied
-
Determine if the device operates in a controlled cellular network environmentReview network configuration and monitor for unauthorized base station connections using cellular network monitoring tools or carrier-provided supervisionAffected if The device can connect to untrusted or unauthorized cellular base stations, which is required to trigger the vulnerability
-
Check for modem crash logs or unexpected resetsReview system logs, modem diagnostic logs, or crash dumps for evidence of unexpected modem behavior or denial of service eventsAffected if The modem has experienced unexplained crashes or resets, which could indicate exploitation attempts
A user is affected if they have a Mediatek Nr15, Nr16, Nr17, or Nr17r modem that has not been patched with firmware MOLY01689251 and can connect to cellular base stations.
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 dataApply the vendor-provided firmware patch (MOLY01689251) to affected modem devices. Monitor for unauthorized base stations in the cellular network environment to prevent rogue base station attacks.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20754 — 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-2025-20754 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