System privilege escalation via out-of-bounds write
Published Mar 16, 2022 · Updated Aug 4, 2024
Out-of-bounds write in Google Titan M on affected Android kernels allows local users with System execution privileges to escalate privileges. A missing bounds check permits a write past the intended memory boundary inside the chip; Google has not disclosed the affected routine. Exploitation requires local access with existing System execution privileges, requires no user interaction, and yields higher privileges on the Pixel device.
Summary
What happened
Out-of-bounds write in Google Titan M on affected Android kernels allows local users with System execution privileges to escalate privileges. A missing bounds check permits a write past the intended memory boundary inside the chip; Google has not disclosed the affected routine. Exploitation requires local access with existing System execution privileges, requires no user interaction, and yields higher privileges on the Pixel device.
The record
- CVE
- CVE-2021-39729
- Published
- Mar 16, 2022
- Updated
- Aug 4, 2024
- Vendor
- Product
- Titan M
- Classifications
- CWE-787, T1404
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Mar 16, 2022CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record 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=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.
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