CVE-2025-20793
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: MOLY01430930; Issue ID: MSV-4836.
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 confidenceThis vulnerability exists in cellular modem firmware where incorrect error handling occurs when the modem processes certain signals from a base station. When a UE (User Equipment) connects to a rogue base station controlled by an attacker, the modem can be triggered to crash due to improper error handling logic, resulting in a denial of service condition.
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 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 modem chipset modelCheck device documentation, system logs, or AT command interface (e.g., AT+CGMM) to determine if the cellular modem uses Mediatek Nr15, Nr16, Nr17, or Nr17r chipsetAffected if The device contains any of these Mediatek modem chipsets (Nr15, Nr16, Nr17, Nr17r)
-
Determine firmware versionQuery the modem firmware version using AT commands (e.g., AT+CGMR) or check system firmware information provided by the device manufacturerAffected if The installed firmware version is present and can be compared to vendor patch MOLY01430930
-
Check if cellular modem is activeVerify that the cellular modem functionality is enabled and operational on the device. This can be done by checking if the modem is registered on a network via AT commands (e.g., AT+CREG?) or through device management interfacesAffected if The cellular modem is powered on and actively connecting to base stations, making it subject to rogue base station signals
-
Inspect for patch implementationReview vendor release notes, device firmware changelogs, or contact the device manufacturer to confirm whether patch MOLY01430930 has been integrated into the current firmware versionAffected if The installed firmware does not include the MOLY01430930 patch
-
Assess base station exposureReview network logs or use spectrum monitoring tools to detect if unauthorized or rogue base stations have been observed connecting to or attempting to connect to the deviceAffected if The device has connected to any base station that is not a known trusted network operator
The environment is affected if the device uses a Mediatek Nr15, Nr16, Nr17, or Nr17r modem chipset and the installed firmware does not include patch MOLY01430930, with the modem actively connecting to cellular networks.
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-provided patch (MOLY01430930) to update modem firmware. Organizations should also implement network monitoring to detect unauthorized or rogue base stations in the area.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20793 — 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-20793 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