CVE-2024-20076
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 with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: MOLY01297806; Issue ID: MSV-1481.
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 is a denial of service vulnerability in the Modem component caused by incorrect error handling. The vulnerability can be exploited remotely without requiring any privileges or user interaction, leading to a system crash. The fix is available via patch ID MOLY01297806.
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 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/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 Lr12a modem hardwareCheck system hardware inventory, device specifications, or modem firmware logs for 'Mediatek' and 'Lr12a' identifiers. On Linux, run 'at+cfun?' via AT command interface or check /proc/cpuinfo for modem-related entries.Affected if Mediatek Lr12a modem is present in the system
-
Check modem firmware versionQuery the modem firmware version via AT command interface (e.g., 'AT+CGMR' or 'AT+GMR') or through the device management interface. Compare the version string to determine if patch MOLY01297806 has been applied.Affected if Firmware version does not include patch MOLY01297806 or version cannot be determined (all versions are affected)
-
Verify modem network exposureReview network configuration to determine if modem interfaces (AT command ports, QMI/RMNET, or radio interfaces) are exposed to untrusted networks or accessible remotely. Check firewall rules and interface bindings.Affected if Modem interface is exposed to network or has external accessibility
-
Check for modem crash indicatorsReview system logs (dmesg, kernel logs, modem-specific logs) for crash reports, panic messages, or unexpected modem resets occurring without clear cause. Look for error patterns related to 'modem', 'lte', or 'radio'.Affected if Recurring modem crashes or system instability is observed without other explanation
If Mediatek Lr12a modem firmware is present without patch MOLY01297806 and the modem interface is network-accessible, the environment is vulnerable to remote denial of service.
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 MOLY01297806 to affected modem firmware. Since this is a remote DoS with no user interaction required, prioritize patching devices with exposed modem interfaces.
- 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-2024-20076 — 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-20076 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