CVE-2024-20131
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 escalation of privilege due to an incorrect bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: MOLY01395886; Issue ID: MSV-1873.
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 local privilege escalation vulnerability exists in the Modem component due to an incorrect bounds check (Issue ID MSV-1873). An attacker with existing System execution privileges can exploit this to gain elevated privileges. No user interaction is required.
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
- Local
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Mediatek modem chipset modelCheck /proc/cpuinfo or use 'getprop ro.mediatek.platform' to determine if the device uses a Mediatek chipset. Look specifically for Nr16 or Nr17 modem components in the system logs or /proc/interrupts for modem-related entries.Affected if Device uses Mediatek Nr16 or Nr17 modem component
-
Check baseband/modem firmware versionQuery the modem firmware version via AT command interface (e.g., echo 'AT+CGMR' > /dev/ttyACM0 or /dev/smd0) or through Android's TelephonyManager API (getBasebandVersion).Affected if Modem firmware version is present and not patched to MOLY01395886 or later
-
Verify current execution privilegesCheck current user ID and groups using 'id' command or check /proc/self/status for Uid, Gid fields. This vulnerability requires System-level privileges as the starting point.Affected if Current process runs with System user privileges (uid 1000) rather than root (uid 0) or unprivileged user
-
Confirm modem component is active and accessibleCheck for presence of modem-related processes (via 'ps -A' looking for rild, vendor.ril, or modem processes) and verify /dev/ directory contains ttyACM*, smd*, or similar modem interfaces.Affected if Modem component is actively running and accessible from System privilege level
A device is affected if it contains a Mediatek Nr16 or Nr17 modem component with unpatched firmware (versions prior to MOLY01395886), and an attacker already has System-level code execution on the device.
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 MOLY01395886 to the affected modem firmware once available. Since this is a modem/baseband component, updates typically come through device manufacturer or carrier firmware releases.
- Consultation3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-20131 — 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-2024-20131 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