CVE-2024-20082
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 memory corruption 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: MOLY01182594; Issue ID: MSV-1529.
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 confidenceA missing bounds check in the modem component allows memory corruption, enabling remote code execution without requiring user interaction or additional privileges. The vulnerability resides in the baseband/modem firmware layer.
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 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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Mediatek modem chipset modelCheck your device's baseband or modem information in phone settings (usually under Settings > About Phone > Baseband/Mobile Network) or via AT command 'AT+CGMM' to query the modem modelAffected if The device uses Mediatek Nr15, Nr16, or Nr17 chipset variants
-
Locate the modem/baseband firmware versionAccess the modem firmware version through device settings (Settings > About Phone > Baseband version) or use AT command 'AT+CGMR' to query the firmware revisionAffected if The displayed firmware version cannot be verified against the patched version MOLY01182594 or later
-
Verify the firmware patch levelCompare the installed baseband/modem firmware version against the patched version MOLY01182594. Note that different carriers may use variant version numbers; check if the version string contains 01182594 or a later date/revisionAffected if The firmware version is lower than MOLY01182594, or the patch has not been applied by the device manufacturer or carrier
-
Confirm the vulnerability is in the modem firmware layerThis vulnerability exists in the baseband/modem firmware itself, not in the application processor OS. Verify you are checking the modem/baseband firmware and not the Android/system versionAffected if The device has a Mediatek Nr15/Nr16/Nr17 modem and the baseband firmware has not been updated
If the device contains a Mediatek Nr15, Nr16, or Nr17 modem chipset and the baseband firmware version is earlier than MOLY01182594, the environment is affected by this vulnerability.
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 (MOLY01182594) to update the modem firmware. Since this is a remote code execution vulnerability in a critical component with no user interaction required, immediate patching is critical.
- Consultation4.0 h
- Implementation2.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-20082 — 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-20082 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