Local privilege escalation via Attestation ID bypass
Published Sep 13, 2024 · Updated Mar 13, 2025
Privilege escalation in Android 14 and affected Pixel devices allows local users to gain elevated execution without user interaction. Multiple legacy.rs locations apply incorrect logic to Attestation ID device protection, permitting a protection bypass. The Android 14 path requires System execution privileges; Google has not disclosed the Pixel pre-install app's root cause.
Summary
What happened
Privilege escalation in Android 14 and affected Pixel devices allows local users to gain elevated execution without user interaction. Multiple legacy.rs locations apply incorrect logic to Attestation ID device protection, permitting a protection bypass. The Android 14 path requires System execution privileges; Google has not disclosed the Pixel pre-install app's root cause.
The record
- CVE
- CVE-2024-29779
- Published
- Sep 13, 2024
- Updated
- Mar 13, 2025
- Vendor
- Product
- Android
- Classifications
- CWE-269, T1404
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 13, 2024CVE publishedPublication date reported by the CVE source.
- Mar 13, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <*
- Affected versionversion=Android kernel
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo