Local privilege escalation via missing Keymaster bounds check
Published Mar 30, 2022 · Updated Aug 4, 2024
Out-of-bounds write in the Keymaster component of Android 12L allows local users with System privileges to escalate privileges without interaction. Keymaster writes past a buffer because the affected operation omits a required bounds check on its input. Exploitation requires local access and System execution privileges, and successful memory corruption grants higher privileges without user interaction.
Summary
What happened
Out-of-bounds write in the Keymaster component of Android 12L allows local users with System privileges to escalate privileges without interaction. Keymaster writes past a buffer because the affected operation omits a required bounds check on its input. Exploitation requires local access and System execution privileges, and successful memory corruption grants higher privileges without user interaction.
The record
- CVE
- CVE-2021-39741
- Published
- Mar 30, 2022
- Updated
- Aug 4, 2024
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-787, T1068
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Mar 30, 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-12L
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