CVE-2025-20752
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 a missing 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: MOLY01270690; Issue ID: MSV-4301.
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 confidenceA missing bounds check in the Modem component allows a remote attacker controlling a rogue base station to crash the UE (User Equipment) device via the cellular network connection. This is a denial of service vulnerability requiring no additional privileges or user interaction, exploiting the lack of input validation when the UE connects to the malicious base station.
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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/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 modem chipset manufacturerQuery the device's modem subsystem or baseband information via AT commands (e.g., AT+CGMM or AT+CGMI) or through system information files in /proc or /sys related to the cellular modemAffected if The chipset is manufactured by Mediatek
-
Determine the specific modem variantCheck the modem model or firmware identifier reported by the device (often via AT+CGMR or through baseband version strings)Affected if The modem variant is Nr15, Nr16, Nr17, or Nr17r
-
Check the installed modem firmware versionRetrieve the baseband firmware version through AT commands (e.g., AT+CGMR) or by examining the modem firmware image metadataAffected if The firmware version is earlier than MOLY01270690 or the patch identifier is absent
-
Verify the modem is actively connected or capable of cellular connectivityConfirm the device has cellular radio enabled and the modem is operational (check for active RRC connection or modem interface presence)Affected if The device has an active cellular radio interface and can connect to base stations
-
Assess exposure to untrusted base stationsReview whether the device connects to cellular networks beyond operator-controlled networks or if it operates in roaming environments with unknown base stationsAffected if The device can connect to or is configured to connect to untrusted or unknown cellular base stations
A device is affected if it contains a Mediatek Nr15, Nr16, Nr17, or Nr17r modem with firmware older than the patched version MOLY01270690, and the cellular radio is active or capable of connecting to 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 vendor patch MOLY01270690 to the affected modem firmware. Users should avoid connecting to untrusted or unknown cellular base stations.
- Consultation4.0 h
- Implementation4.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 $5,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20752 — 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-20752 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