Local privilege escalation via missing AES-GCM bounds check
Published Dec 15, 2021 · Updated Aug 3, 2024
Out-of-bounds write in Google Titan M Android kernel firmware allows local users to escalate privileges through AES-GCM decryption. The eicOpsDecryptAes128Gcm routine in acropora/app/identity/identity_support.c writes beyond a buffer because it omits a bounds check on decryption data. A local low-privileged process can trigger the corruption without user interaction, and successful exploitation grants higher privileges on the device.
Summary
What happened
Out-of-bounds write in Google Titan M Android kernel firmware allows local users to escalate privileges through AES-GCM decryption. The eicOpsDecryptAes128Gcm routine in acropora/app/identity/identity_support.c writes beyond a buffer because it omits a bounds check on decryption data. A local low-privileged process can trigger the corruption without user interaction, and successful exploitation grants higher privileges on the device.
The record
- CVE
- CVE-2021-1044
- Published
- Dec 15, 2021
- Updated
- Aug 3, 2024
- Vendor
- Product
- Titan M
- Classifications
- CWE-787, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 15, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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