dbcve.org
AndroidOperating system · Google

CVE-2024-47012

HIGH · 7.8 CVSS v3.1 Published 2024-10-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
In mm_GetMobileIdIndexForNsUpdate of mm_GmmPduCodec.c, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

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 confidence

A bounds check error in the mm_GetMobileIdIndexForNsUpdate function within the GMM PDU codec causes an out-of-bounds write, enabling local privilege escalation without user interaction or additional execution privileges. This vulnerability resides in the mobile device's baseband/modem firmware layer handling 3GPP mobility management protocols.

MitigationApply vendor-supplied firmware/security patches to update the baseband modem; no workarounds available as this is a memory safety flaw in the core modem code.

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 data
AndroidOperating system
Affected:all versions

CVSS 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check baseband/modem firmware version
    Navigate to Settings > About Phone > SIM Status, or use AT command 'AT+CGMR' via a terminal app or serial connection to query the modem firmware version
    Affected if The baseband firmware version is unknown, unpatched, or predates the vendor security patch released for CVE-2024-47012 (contact your device/vendor for specific version details)
  2. Identify modem chipset vendor
    Determine the baseband/modem chipset manufacturer (Qualcomm, MediaTek, Samsung LSI, HiSilicon, etc.) either from device specifications or via 'getprop' commands such as 'getprop ro.baseband.platform' or 'getprop ro.vendor.mpdecision.major'
    Affected if The device uses a baseband chipset where the vendor has not released CVE-2024-47012 patches for the specific modem firmware version
  3. Confirm vulnerability is in baseband layer
    Verify this is a baseband/modem firmware vulnerability by understanding it affects the 3GPP mobility management (GMM) protocol handler in the modem, not the Android application processor or OS kernel
    Affected if The device processes 3GPP mobility management messages through the baseband modem (this is true for virtually all cellular-capable Android devices)

A user is affected if their Android device has a baseband/modem firmware version that has not been patched by the chipset/vendor to address the out-of-bounds write in mm_GetMobileIdIndexForNsUpdate within the GMM PDU codec.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied firmware/security patches to update the baseband modem; no workarounds available as this is a memory safety flaw in the core modem code.

Recommended fix Moderate confidence

Android Security Patch Level as specified in the official Android Security Bulletin for CVE-2024-47012

  1. Check the Android Security Bulletin for CVE-2024-47012 at source.android.com/security/bulletin to identify the specific Android Security Patch Level that contains the fix
  2. Apply the latest Android system update or security patch for your device from your device manufacturer or carrier
  3. Verify the installed Android Security Patch Level meets or exceeds the level listed in the security bulletin for this vulnerability
  4. For devices no longer receiving official security updates, consider upgrading to a device that receives regular security patches
Caveat Devices that are no longer supported by manufacturers may not receive security patches; consider upgrading to a supported device

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,080.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-47012 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-47012 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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