Local privilege escalation via camera use after free
Published Apr 12, 2022 · Updated Aug 4, 2024
Use-after-free in Google Pixel camera components allows local users to gain privileges through affected Android kernel processing. The camera component performs an out-of-bounds read after a freed object is reused, creating the memory-safety condition. Exploitation requires a local user on the device without user interaction or additional execution privileges and can result in escalation of privilege.
Summary
What happened
Use-after-free in Google Pixel camera components allows local users to gain privileges through affected Android kernel processing. The camera component performs an out-of-bounds read after a freed object is reused, creating the memory-safety condition. Exploitation requires a local user on the device without user interaction or additional execution privileges and can result in escalation of privilege.
The record
- CVE
- CVE-2021-39812
- Published
- Apr 12, 2022
- Updated
- Aug 4, 2024
- Vendor
- Product
- Google Pixel
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 12, 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