CVE-2025-20762
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 incorrect error handling. 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: MOLY01685181; Issue ID: MSV-4760.
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 confidenceDenial of service vulnerability in Modem component due to incorrect error handling. Exploitable remotely when User Equipment (UE) connects to an attacker-controlled rogue base station, causing system crash without requiring additional privileges or user interaction. This is a baseband/modem firmware vulnerability.
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 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 Mediatek Nr17 modem presenceCheck device specifications, system information, or modem diagnostics to determine if the device contains a Mediatek Nr17 baseband/modem component. This may be visible in device specs, modem info under settings, or via AT command interface (e.g., AT+CGMM or ATI).Affected if Device contains Mediatek Nr17 modem hardware
-
Confirm modem firmware versionQuery the modem firmware version using device-specific methods such as AT commands (e.g., AT+CGMR), system diag logs, or modem info in settings. Compare the firmware version against any available version information from the vendor.Affected if Any Mediatek Nr17 firmware version is present (all versions are affected)
-
Assess rogue base station exposureReview network connection logs or monitor for unexpected cell tower connections. Determine if the device has connected to or is susceptible to connecting to untrusted or suspicious base stations.Affected if Device can connect to cellular networks controlled by untrusted parties
If the device contains a Mediatek Nr17 modem component and operates in an environment where it may connect to untrusted base stations, the environment is affected by this vulnerability.
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.
dbcve · scopedApply vendor patch MOLY01685181 via firmware update from device manufacturer. Avoid connecting UE devices to untrusted or suspicious base stations until patch is deployed.
- Contact your device OEM (Original Equipment Manufacturer) to request the MediaTek modem firmware patch MOLY01685181
- Confirm with your OEM that the patch MSV-4760 has been applied to your device's modem firmware
- If you are an OEM or module integrator, obtain the MOLY01685181 patch from MediaTek and integrate it into your modem firmware build
- Apply the updated modem firmware to affected devices
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20762 — 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-20762 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