CVE-2025-20759
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 read 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: MOLY01673760; Issue ID: MSV-4650.
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 confidenceAn out of bounds read vulnerability exists in the Modem component due to a missing bounds check. When a User Equipment (UE) connects to a rogue base station controlled by an attacker, this could lead to remote denial of service without requiring any additional execution 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 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 device modem chipsetCheck the device specifications or system information to determine if the device uses a MediaTek modem. This can typically be found in the device's hardware specifications, About Phone section, or by querying the modem via AT commands (e.g., AT+CGMR or ATI) if accessible.Affected if The device uses a MediaTek Nr15 or Nr16 modem component.
-
Confirm modem variantQuery the modem firmware for the specific variant identifier. On Android devices, this may be visible in the baseband version string or through engineering mode menus. Look for references to Nr15 or Nr16 in the modem firmware information.Affected if The modem firmware identifies itself as Mediatek Nr15 or Mediatek Nr16.
-
Check baseband firmware versionRetrieve the baseband/modem firmware version from the device. On Android: Settings > About Phone > Baseband version. Via ADB: getprop gsm.version.baseband or getprop ro.mediatek.version.release. Note the full version string.Affected if The device has any baseband version installed on a Mediatek Nr15 or Nr16 modem, as all versions are affected per the advisory.
-
Verify rogue base station exposureAssess whether the device is likely to connect to untrusted cellular base stations. This applies particularly to devices used in roaming scenarios, testing environments, or devices with basestation simulation capabilities nearby.Affected if The device can connect to or scan for cellular networks, as the vulnerability is triggered upon connection to a rogue base station.
A device is affected if it contains a MediaTek Nr15 or Nr16 modem component with any firmware version, as all versions of these modems are vulnerable to the out-of-bounds read when connecting to a rogue base station.
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 MOLY01673760. Additionally, advise users to avoid connecting to untrusted or rogue base stations to reduce attack surface.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20759 — 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-20759 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