dbcve.org
AndroidOperating system · Google

CVE-2024-47021

HIGH · 7.5 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 →
84/100
Remediation priority · High
Remotely reachable No privileges 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 sms_ExtractCbLanguage of sms_CellBroadcast.c, there is a possible out of bounds read due to a missing bounds check. This could lead to remote information disclosure 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 · high confidence

An out-of-bounds read vulnerability exists in the sms_ExtractCbLanguage function of Android's sms_CellBroadcast.c component due to a missing bounds check when processing Cell Broadcast messages. This allows remote attackers to read sensitive memory contents beyond intended buffers, leading to information disclosure without requiring user interaction or elevated privileges.

MitigationApply the latest Android security patch from the Google Android Security Bulletin that addresses CVE-2024-47021. Users should ensure their devices receive and install system updates promptly.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 Android Security Patch Level
    Go to Settings > About Phone > Security Patch Level (or Settings > System > Security Update on some devices). Record the date shown.
    Affected if The Security Patch Level date is earlier than the patch date for CVE-2024-47021 (check the Android Security Bulletin for the specific release date).
  2. Verify Cell Broadcast module is present
    Check that the device has SMS/Cell Broadcast capability. Most Android devices have this enabled by default for receiving emergency and public warning messages. This can be verified by examining /system/framework/framework-res.apk or the base system image for the sms_CellBroadcast.c component.
    Affected if The Cell Broadcast component exists on the device (which is true for virtually all Android phones).
  3. Check Android version as secondary indicator
    Navigate to Settings > About Phone > Android version. Note the version number.
    Affected if Any Android version is potentially affected since the affected products list states 'all versions'. The device is only safe if the Security Patch Level indicates the fix has been applied.
  4. Check for incoming Cell Broadcast messages
    Monitor if the device receives Cell Broadcast (CB) or Emergency Alerts messages. These are typically received automatically by the baseband/modem and processed by the android framework.
    Affected if The device processes Cell Broadcast messages (default behavior for all Android devices). The vulnerability is triggered during CB message processing regardless of whether the user views the message.

The device is affected if the Android Security Patch Level predates the fix release for CVE-2024-47021, as this is a base system vulnerability in the Cell Broadcast handling code present across all Android versions.

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 the latest Android security patch from the Google Android Security Bulletin that addresses CVE-2024-47021. Users should ensure their devices receive and install system updates promptly.

Recommended fix Moderate confidence

Latest available Android security patch level for your device (refer to Android Security Bulletin for CVE-2024-47021 publication date)

  1. Check the Android Security Bulletin for the month this CVE was addressed to identify the specific patch level containing the fix
  2. Apply the latest Android system security update available for your device via Settings > Security > Security update
  3. If your device no longer receives official security updates, consider upgrading to a device that still receives monthly security patches
  4. For enterprise/managed devices, ensure mobile device management (MDM) policies enforce automatic security updates
Caveat Some older devices may stop receiving security updates entirely; ensure app compatibility before upgrading OS major versions

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

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-47021 — 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-47021 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