dbcve.org
AndroidOperating system · Google

CVE-2024-47020

HIGH · 7.5 CVSS v3.1 Published 2024-10-25
Fix available
A fix is available. Upgrade to 2024-10-05 or later.
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
Android before 2024-10-05 on Google Pixel devices allows information disclosure in the ABL component, A-331966488.

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 information disclosure vulnerability exists in the ABL (Android Boot Loader) component of Google Pixel devices running Android versions before the October 2024 security patch. The ABL runs early in the device boot process and handles critical secure boot operations; successful exploitation could expose sensitive boot-time information such as secure boot parameters, device secrets, or cryptographic material.

MitigationApply the October 2024 Android security patch (or later) to all affected Google Pixel devices to address the vulnerability in the ABL component. Organizations should verify patch deployment status across their device fleet.

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:< 2024-10-05

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. Identify the device model
    Check if the device is a Google Pixel by viewing the device model in Settings > About Phone > Model Number, or by running 'getprop ro.product.model' via ADB
    Affected if Device is NOT a Google Pixel device - this vulnerability specifically affects Google Pixel devices only
  2. Check the Android version
    Navigate to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB
    Affected if Android version is 14 or lower (the exact version depends on when the October 2024 patch was applied to each version)
  3. Verify the security patch level
    Navigate to Settings > About Phone > Security patch level, or run 'getprop ro.build.version.security_patch' via ADB
    Affected if Security patch level shows a date BEFORE October 5, 2024 (e.g., September 2024, August 2024, etc.)
  4. Confirm ABL component is present
    Verify the device boots with ABL by checking 'getprop ro.boot.abl' or 'ls /dev/block/bootdevice/by-name/abl' via ADB (ABL is present on Pixel devices with legacy bootloader architecture)
    Affected if Device lacks ABL component - this vulnerability is specific to the ABL bootloader component

A Google Pixel device is affected if it shows a security patch level dated before October 5, 2024.

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
Upgrade available Upgrade to 2024-10-05 or later
Fixed in 2024-10-05
Interim mitigation

Apply the October 2024 Android security patch (or later) to all affected Google Pixel devices to address the vulnerability in the ABL component. Organizations should verify patch deployment status across their device fleet.

Recommended fix Moderate confidence

Android version 2024-10-05 or later on Google Pixel devices

  1. 1. Navigate to Settings > System > System Update on your Google Pixel device
  2. 2. Check for available updates and ensure the update with date 2024-10-05 or later is installed
  3. 3. If no update is available, ensure your device is connected to Wi-Fi and has adequate battery charge, then check again
  4. 4. Download and install the system update
  5. 5. After installation completes, verify the update was applied by checking the Android security patch level in Settings > About Phone > Android version

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

Fix this in Android Scoped from the published advisory
  • Consultation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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