CVE-2024-20077
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: MOLY01297807; Issue ID: MSV-1482.
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 denial of service vulnerability exists in the Modem component due to incorrect error handling that can cause a system crash. The issue can be exploited remotely without requiring elevated privileges or user interaction, making it readily exploitable in the field.
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 hardwareQuery the device or system information to determine if the modem hardware is Mediatek Lr12a. This may be listed in system specs, boot logs, or modem identification commands such as AT+CGMM or ATI3Affected if The device contains a Mediatek Lr12a modem component
-
Retrieve modem firmware versionExecute an AT command to query the modem firmware version, such as AT+CGMR or AT+CGMM, or check the baseband/modem firmware information in the system boot logsAffected if The installed modem firmware version corresponds to the Lr12a platform (all versions are affected)
-
Check for modem crash indicatorsReview system logs, kernel logs, or modem diagnostic logs for evidence of unexpected modem crashes, resets, or system crashes originating from the modem componentAffected if Modem-related crashes or system instability are observed and the device uses Lr12a hardware
A system is affected if it contains a Mediatek Lr12a modem component, regardless of firmware version, as all versions of this platform are vulnerable to the denial of service flaw.
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.
dbcve · scopedApply the vendor-supplied patch (MOLY01297807) to update the modem firmware, as this is a firmware-level issue in the baseband/modem subsystem.
- 1. Contact MediaTek directly or your MediaTek OEM/ODM vendor to request the patch MOLY01297807
- 2. Verify the patch is applicable to your specific Lr12a modem firmware version
- 3. Obtain the patched firmware image from MediaTek or your device vendor
- 4. Follow the standard MediaTek firmware update procedure for Lr12a modem devices
- 5. After applying the patch, verify the modem operates normally and confirm the vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-20077 — 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-20077 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