dbcve.org
AndroidOperating system · Google

CVE-2024-47039

MEDIUM · 5.5 CVSS v3.1 Published 2024-12-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
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 isSlotMarkedSuccessful of BootControl.cpp, there is a possible out of bounds read due to a missing bounds check. This could lead to local  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

In Android's boot control implementation (BootControl.cpp), the isSlotMarkedSuccessful function lacks proper bounds validation when accessing slot metadata, allowing an out-of-bounds read that can expose sensitive memory contents locally without requiring elevated privileges or user interaction.

MitigationApply bounds checking in the isSlotMarkedSuccessful function to validate array indices before accessing slot information, ensuring read operations stay within allocated buffer boundaries.

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:= 10.0

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
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/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 version
    Run 'getprop ro.build.version.release' in a terminal or check Settings > About Phone > Android version
    Affected if Version is exactly 10.0 (the only affected version)
  2. Check if A/B slot partitioning is enabled
    Run 'getprop ro.boot.slot_suffix' - if it returns a value like '_a' or '_b', A/B slotting is active; alternatively check /dev/block/bootdevice/by-name/ for boot_a and boot_b entries
    Affected if A/B slot partitioning is enabled, as this is required for the isSlotMarkedSuccessful function to process slot metadata
  3. Verify BootControl HAL is accessible
    Check for the presence of /vendor/etc/init/[email protected]* or run 'lshal | grep boot' to list boot control HAL clients
    Affected if BootControl HAL is running and accessible on the device

Device is affected if running Android 10.0 with A/B slot partitioning enabled, since the vulnerable isSlotMarkedSuccessful function processes slot metadata in this configuration

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 bounds checking in the isSlotMarkedSuccessful function to validate array indices before accessing slot information, ensuring read operations stay within allocated buffer boundaries.

Recommended fix Moderate confidence

Android 11 or later (Android 13/14 recommended) with October 2024 Security Patch Level or later

  1. Check the Android Security Bulletin for CVE-2024-47039 to identify the specific Android version or security patch level that contains the fix
  2. Verify your device model and its current Android version by navigating to Settings > About Phone > Android version
  3. If your device manufacturer has released an update containing the security patch for this CVE, apply the system update through Settings > System > Software Update
  4. If no manufacturer update is available, consider upgrading to a newer Android version (Android 12, 13, or 14) that includes the fix
  5. After updating, confirm the security patch level has been incremented to include the fix (typically the October 2024 or later Android Security Patch Level)
Caveat Upgrading Android versions may cause incompatibility with older applications or require data backup due to factory reset requirements on some devices

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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