CVE-2024-20067
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 out of bounds write due to improper input invalidation. This could lead to remote denial of service with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: MOLY01267285; Issue ID: MSV-1462.
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 critical out-of-bounds write vulnerability exists in the modem component due to improper input validation. The flaw allows remote attackers to trigger a denial of service condition without requiring any authentication or user interaction. The vulnerability is addressed by patch MOLY01267285.
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
- 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 Mediatek modem hardware in your environmentCheck system documentation, hardware inventory, or use commands like 'at+cgmm' (for AT-compatible modems) or 'lsusb' / 'lspci' to enumerate modem devices. Look for entries containing 'MediaTek', 'Nr16', or 'Nr17'.Affected if The device contains a Mediatek Nr16 or Nr17 modem component
-
Retrieve modem firmware versionUse modem AT commands such as 'at+cgmr' or 'ati' to query the firmware version. On Linux, check /dev/ttyUSB* or /dev/cdc-* interfaces. On Android, check via 'at+cgmr' through dialer or engineering mode.Affected if The returned firmware version does not reflect patch MOLY01267285 or cannot be verified as patched
-
Check vendor security advisories for patch statusConsult MediaTek's security advisory for CVE-2024-20067. Cross-reference your modem firmware version against the patched version notation MOLY01267285.Affected if You cannot confirm the patch MOLY01267285 has been applied to your modem firmware
-
Verify firmware update mechanism availabilityCheck if your device supports firmware updates for the modem component. Review device settings, carrier firmware update options, or manufacturer-provided update tools.Affected if The modem firmware cannot be updated or version-checked through available tools
You are affected if your environment contains a Mediatek Nr16 or Nr17 modem and the installed firmware does not reflect the MOLY01267285 patch.
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-supplied patch (MOLY01267285) to update the modem firmware on all affected devices. Since this is a remote, unauthenticated denial-of-service vulnerability with no user interaction required, priority patching is critical.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-20067 — 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-20067 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