CVE-2025-20727
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 heap buffer overflow. 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 not needed for exploitation. Patch ID: MOLY01672601; Issue ID: MSV-4623.
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 confidenceHeap buffer overflow in modem firmware allows remote code execution when a device connects to a rogue base station. The vulnerability enables privilege escalation without user interaction or additional 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 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/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 Mediatek modem presenceCheck device documentation, system logs, or modem interface (e.g., /proc/cpuinfo, lsusb, or AT+CGMM command) for Mediatek modem identifiersAffected if Device contains a Mediatek modem chip from the Lr12a, Nr15, Nr16, Nr17, or Nr17r product lines
-
Query modem firmware versionSend AT command to modem (e.g., AT+CGMR or ATI) or read from /proc/mtk_thermal or /sys/class/net/*/device/firmware_version depending on deviceAffected if Unable to retrieve version or version returns any value on affected modem models
-
Confirm affected modem modelQuery modem model using AT+CGMM or AT+CGIA and verify it matches Lr12a, Nr15, Nr16, Nr17, or Nr17rAffected if Modem model is one of the five listed products regardless of version number
-
Compare firmware to patched versionCompare installed firmware version against vendor patch MOLY01672601 - check if version is earlier than this patch levelAffected if Firmware version is present but is any version prior to MOLY01672601, or if version cannot be determined (all versions of affected products are vulnerable)
A user is affected if their device contains a Mediatek Lr12a, Nr15, Nr16, Nr17, or Nr17r modem with any firmware version earlier than MOLY01672601.
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 MOLY01672601 through firmware update. Organizations should monitor for vendor updates and ensure mechanisms exist for deploying modem firmware patches to affected devices.
- Consultation8.0 h
- Implementation24.0 h
- Testing32.0 h
- Review / QA16.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $21,760.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20727 — 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-20727 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