dbcve.org
Nr16Operating system · Mediatek

CVE-2025-20634

CRITICAL · 9.8 CVSS v3.1 Published 2025-02-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
In Modem, there is a possible out of bounds write due to a missing bounds check. This could lead to remote code execution, 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: MOLY01289384; Issue ID: MSV-2436.

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 confidence

Out-of-bounds write vulnerability in the modem component due to missing bounds checking. Allows remote code execution when a user equipment device connects to an attacker-controlled rogue base station, requiring no user interaction or additional privileges.

MitigationApply vendor patch MOLY01289384 to modem firmware. Users should avoid connecting to untrusted or unknown cellular base stations.

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 data
Nr16Operating system
Affected:all versions
Nr17Operating system
Affected:all versions
Nr17rOperating system
Affected:all versions

CVSS 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
High
Availability
High

CVSS:3.1/AV:N/AC:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the modem chipset model
    Check your device specifications, manual, or product page for the modem/baseband chipset. Look for mentions of Mediatek Nr16, Nr17, or Nr17r. On Android, you may find this in Settings > About Phone > Baseband or under FCC ID documentation.
    Affected if The device uses Mediatek Nr16, Nr17, or Nr17r as the modem chipset
  2. Check if the device has received firmware update MOLY01289384
    Contact your device manufacturer or mobile carrier to verify if the security patch MOLY01289384 has been applied to the modem firmware. Check carrier or OEM support pages for firmware update history.
    Affected if The modem firmware has not received the MOLY01289384 patch (all unpatched devices are affected)
  3. Verify baseband firmware version
    On Android, go to Settings > About Phone and record the Baseband version. On feature phones or via terminal, you may be able to run 'AT+CGMR' or 'AT+CGMM' to query the modem version. Compare this against any vendor release notes referencing the patch.
    Affected if The baseband version does not reflect the patched firmware from your carrier or vendor

You are affected if your device contains a Mediatek Nr16, Nr17, or Nr17r modem chipset and the MOLY01289384 patch has not been applied by your carrier or device vendor.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patch MOLY01289384 to modem firmware. Users should avoid connecting to untrusted or unknown cellular base stations.

Recommended fix Moderate confidence

Firmware update from device OEM containing patch MOLY01289384 (MSV-2436)

  1. Contact your device OEM (Original Equipment Manufacturer) to request the patched firmware incorporating MediaTek patch MOLY01289384
  2. Confirm with the OEM that the firmware includes the MSV-2436 fix for the out-of-bounds write vulnerability
  3. Apply the firmware update through the OEM's standard update mechanism
  4. Verify the modem firmware version after update matches the patched release
Caveat Firmware updates may require device downtime and should be tested in a non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Nr16 Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing16.0 h
  • Review / QA8.0 h
42.0 hours of engineering $7,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,520.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-20634 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-20634 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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