Chip code execution via truncated offset check
Published Jun 15, 2022 · Updated Aug 3, 2024
Out-of-bounds write in Google Titan M firmware allows local users with System privileges to execute code on the security chip. The Keymaster parameter parser truncates a DIGEST integer for validation but uses the full value as a stack-buffer offset, writing 0x01 out of bounds. Exploitation requires System-level access to submit crafted Keymaster requests and permits chip code execution and protected-key disclosure.
Summary
What happened
Out-of-bounds write in Google Titan M firmware allows local users with System privileges to execute code on the security chip. The Keymaster parameter parser truncates a DIGEST integer for validation but uses the full value as a stack-buffer offset, writing 0x01 out of bounds. Exploitation requires System-level access to submit crafted Keymaster requests and permits chip code execution and protected-key disclosure.
The record
- CVE
- CVE-2022-20233
- Published
- Jun 15, 2022
- Updated
- Aug 3, 2024
- Vendor
- Product
- Titan M
- Classifications
- CWE-787, T1068
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jun 15, 2022CVE 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
- Quarkslab Titan M exploitfunctional · demonstrated
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