CVE-2025-20667
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 information disclosure due to incorrect error handling. This could lead to remote information disclosure, 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: MOLY01513293; Issue ID: MSV-2741.
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 vulnerability in the modem component allows information disclosure due to incorrect error handling. When a User Equipment (UE) connects to a rogue base station controlled by an attacker, sensitive information can be disclosed remotely without requiring additional privileges or user interaction.
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 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
- 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.
-
Identify the modem chipsetCheck device specifications or system information to determine if the device uses a Mediatek modem. On Android, go to Settings > About Phone > Baseband or use AT command 'AT+CGMR' via a terminal app with modem access.Affected if The device contains a Mediatek Lr12a, Lr13, Nr15, Nr16, Nr17, or Nr17r modem chip.
-
Check modem firmware versionAccess modem version through device settings (Settings > About Phone > Baseband/MODEM) or send AT command 'AT+CGMR' to the modem. Record the firmware version string shown.Affected if The firmware version is present but no vendor patch (MOLY01513293) has been applied, or the version cannot be verified.
-
Verify carrier firmware updatesCheck for system updates from your mobile carrier. Navigate to Settings > System > Software Update or Settings > About Phone > Software Update and note the last update date and any available updates.Affected if No carrier update has been applied or the update history does not indicate the vendor patch has been incorporated.
-
Confirm cellular network exposureVerify that the device has cellular connectivity capability and is actively connected to or has connected to cellular networks. Check Settings > Network & Internet > Mobile Network.Affected if The device connects to cellular networks, as the vulnerability is triggered when connecting to a rogue base station.
The device is affected if it contains any of the listed Mediatek modem chips (Lr12a, Lr13, Nr15, Nr16, Nr17, Nr17r) and the vendor patch (MOLY01513293) has not been applied via carrier firmware update.
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 patch (MOLY01513293) to affected modem firmware. Users should rely on carrier-provided updates and avoid connecting to untrusted cellular networks where possible.
- Consultation4.0 h
- Implementation6.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20667 — 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-20667 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