CVE-2025-20704
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 out of bounds write due to a missing bounds check. This could lead to remote escalation of privilege, if a UE has connected to a rogue base station controlled by the attacker, with no additional execution privileges needed. User interaction is needed for exploitation. Patch ID: MOLY01516959; Issue ID: MSV-3502.
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 confidenceIn Modem firmware, a missing bounds check allows an out-of-bounds write. When a user equipment (UE) connects to an attacker-controlled rogue base station, the malformed communications trigger this vulnerability, potentially allowing remote privilege escalation without requiring additional execution privileges.
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 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:H/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/baseband processor modelCheck the device's baseband processor information. On Android devices, this is typically found under Settings > About Phone > Baseband version, or via diagnostic codes like *#*#3646633#*#*. Alternatively, use ADB command: 'adb shell getprop ro.baseband' or 'adb shell cat /proc/version' to identify the baseband chipAffected if The device shows Mediatek Nr17 or Mediatek Nr17r as the baseband/modem model
-
Retrieve the current modem firmware versionQuery the baseband firmware version using AT commands (connect via serial terminal or diagnostic port with command 'AT+CGMR' or 'AT+VER') or check the baseband version displayed in the device settings under About Phone > Modem version or Baseband versionAffected if A version number is returned but the patch identifier MOLY01516959 is not shown or the version is earlier than the patched release
-
Verify if the vendor patch has been appliedCheck the firmware changelog, modem build information, or contact the device manufacturer documentation to confirm if the patch MOLY01516959 is included. The patched version typically displays the patch identifier or a version number post-patchAffected if The patch identifier MOLY01516959 is not present in the firmware version string or build information
-
Check for rogue base station exposureReview network connection logs or use mobile network scanning tools to identify if the device has previously connected to untrusted or unknown base stations. This vulnerability is triggered specifically when connecting to attacker-controlled rogue base stationsAffected if The device has connected to unrecognized or suspicious base stations, particularly in testing or untrusted network environments
A device is affected if it uses Mediatek Nr17 or Nr17r modem firmware and the patch MOLY01516959 has not been applied, regardless of the specific firmware version.
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-supplied firmware patch (MOLY01516959) to the modem/baseband processor. Users should avoid connecting to unknown or untrusted base stations until the patch is deployed.
- Consultation4.0 h
- Implementation6.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 $6,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20704 — 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-20704 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