CVE-2024-47022
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 · uneditedAndroid before 2024-10-05 on Google Pixel devices allows information disclosure in the ACPM component, A-331255656.
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 confidenceThis is an information disclosure vulnerability in the ACPM (Android Central Power Manager) component affecting Google Pixel devices running Android versions prior to the October 2024 security patch. The flaw allows unauthorized parties to potentially access sensitive information through the power management subsystem.
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< 2024-10-05CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify device modelCheck if the device is a Google Pixel by going to Settings > About Phone and looking for 'Pixel' in the model name or manufacturerAffected if Device is NOT a Google Pixel device - only Pixel devices are affected
-
Check Android security patch levelGo to Settings > About Phone > Android version and look at the 'Security patch' date. Alternatively, run 'adb shell getprop ro.build.version.security_patch'Affected if Security patch level is earlier than 2024-10-05 (October 5, 2024)
-
Verify Android versionGo to Settings > About Phone > Android version to confirm the Android OS version. Alternatively, run 'adb shell getprop ro.build.version.release'Affected if Android version is below the level that received the October 2024 patch
-
Confirm ACPM component presenceVerify the Android Central Power Manager subsystem is present on the device. Run 'adb shell pm list packages | grep -i power' or check for ACPM-related services in the systemAffected if ACPM component is present and the device meets the version criteria above
A device is affected if it is a Google Pixel running Android with a security patch level before October 5, 2024, and the ACPM power management component is present on the device.
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 · scoped2024-10-05
Apply the October 2024 or later Android security update on affected Google Pixel devices to remediate this vulnerability.
Android with October 2024 security patch level (2024-10-05) or later on Google Pixel devices
- 1. Check your current Android security patch level by going to Settings > About Phone > Android version
- 2. Ensure your Google Pixel device is connected to Wi-Fi
- 3. Go to Settings > System > Software update
- 4. Check for updates and download/install the October 2024 security update or later
- 5. After installation, verify the security patch level shows 2024-10-05 or later in Settings > About Phone > Android version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2024-47022 — 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-47022 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