CVE-2024-20039
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 protocol, there is a possible out of bounds write due to a missing bounds check. This could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: MOLY01240012; Issue ID: MSV-1215.
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 confidenceAn out-of-bounds write vulnerability in the modem protocol due to a missing bounds check allows remote code execution without requiring additional privileges or user interaction. The vulnerability exists in the baseband/modem processor firmware.
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 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 the Mediatek modem chip modelCheck the device specifications or system information to determine if the device uses a Mediatek Lr12a, Lr13, Nr15, Nr16, or Nr17 baseband/modem processor. This information is typically found in the device's technical documentation, FCC filing, or by querying the baseband processor information through AT commands (e.g., AT+CGMM or ATI) if available.Affected if The device contains any of these Mediatek chip models: Lr12a, Lr13, Nr15, Nr16, or Nr17.
-
Query the baseband firmware versionRetrieve the current modem/baseband firmware version. On many devices, this can be done via AT commands (e.g., AT+CGMR or AT+CGINFO) or through system diagnostic tools. Alternatively, check the device settings under About Phone > Baseband or SIM status information.Affected if The firmware version cannot be determined or is older than the patched version MOLY01240012.
-
Verify if the vulnerability patch has been appliedCompare the installed baseband/modem firmware version against the patched version MOLY01240012. The patch version may be displayed in the firmware build string or baseband version information. Note that some devices may display version strings differently (e.g., as part of a larger build number).Affected if The installed firmware version is below MOLY01240012 or the patch version is not explicitly listed in the baseband version information.
-
Check if the device receives cellular/mobile network servicesConfirm that the device has an active cellular modem capability and connects to mobile networks. This vulnerability affects the baseband processor, so devices without cellular functionality (Wi-Fi only devices) are not affected.Affected if The device has an active cellular modem and uses one of the affected Mediatek chips.
A device is affected if it contains a Mediatek Lr12a, Lr13, Nr15, Nr16, or Nr17 baseband processor with firmware version below MOLY01240012.
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 patch (MOLY01240012) through a firmware update from the device manufacturer once available.
- Consultation2.0 h
- Implementation4.0 h
- Testing8.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,288.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-20039 — 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-20039 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