CVE-2024-20154
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 a missing bounds check. This could lead to remote code execution, if a UE has connected to a rogue base station controlled by the attacker, with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: MOLY00720348; Issue ID: MSV-2392.
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 an out-of-bounds write when a User Equipment (UE) connects to a rogue base station. This can lead to remote code execution without requiring user interaction or additional privileges, as the attack exploits the cellular base station communication protocol.
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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/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 modelCheck device system info or modem firmware details for one of these identifiers: Lr12a, Lr13, Nr16.r1.mp, Nr16.r1.mp1mp2.mp, or Nr16.r2.mp. On Android, this often appears in Settings > About Phone > Baseband version or via AT command 'AT+CGMR' sent to the modem serial port.Affected if The modem model matches any of the five listed variants (Lr12a, Lr13, Nr16.r1.mp, Nr16.r1.mp1mp2.mp, or Nr16.r2.mp).
-
Verify modem firmware versionQuery the modem firmware version using AT command 'AT+CGMR' or check the baseband version displayed in the device settings under About Phone > Baseband or Modem version.Affected if The displayed firmware version is present and the modem is a Mediatek chipset from the affected product list - note that all versions of these products are affected.
-
Confirm cellular connectivity is enabledCheck whether the device has mobile data or cellular radio enabled. This can be verified through device settings or by observing active cellular network registration.Affected if Cellular connectivity is active - the vulnerability triggers when the UE (User Equipment) connects to a base station, so an active cellular interface is required for exploitation.
-
Assess exposure to untrusted base stationsEvaluate whether the device operates in environments where it might connect to untrusted or unknown cellular base stations (e.g., traveling, roaming, or areas with unfamiliar cell towers).Affected if The device connects to cellular networks in any capacity - the vulnerability is triggered specifically during the base station connection process.
A device is affected if it contains any of the Mediatek modem models (Lr12a, Lr13, Nr16.r1.mp, Nr16.r1.mp1mp2.mp, or Nr16.r2.mp) and has cellular connectivity enabled, since all versions of these products are vulnerable to out-of-bounds write when connecting to a rogue base station.
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 patch (MOLY00720348) via firmware update from the device OEM. Until the patch is available, avoid connecting mobile devices to untrusted or unknown cellular base stations.
Contact Mediatek or your device vendor for the specific fixed firmware release - patch ID MOLY00720348
- 1. Contact Mediatek directly or through your device/vendor representative to obtain the firmware patch for Patch ID MOLY00720348 (Issue ID MSV-2392)
- 2. Request the specific fixed firmware version for affected modem products: Lr12a, Lr13, Nr16.r1.mp, Nr16.r1.mp1mp2.mp, and Nr16.r2.mp
- 3. Obtain the patched modem firmware from Mediatek or your device OEM
- 4. Apply the firmware update following the vendor's documented upgrade procedure for your specific device
- 5. Verify the patch has been successfully applied by checking the modem firmware version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.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 $4,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-20154 — 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-20154 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