Physical privilege escalation via bootROM bounds error
Published Jun 14, 2021 · Updated Aug 3, 2024
Out-of-bounds write in Chromecast bootROM on Android SoC allows physically proximate attackers to escalate bootloader privileges via USB. The bootROM applies an incorrect bounds check before a write, allowing USB-supplied data to be written beyond the intended buffer. Exploitation requires physical USB access but no existing execution privileges or user interaction, and successful exploitation gains elevated bootloader control.
Summary
What happened
Out-of-bounds write in Chromecast bootROM on Android SoC allows physically proximate attackers to escalate bootloader privileges via USB. The bootROM applies an incorrect bounds check before a write, allowing USB-supplied data to be written beyond the intended buffer. Exploitation requires physical USB access but no existing execution privileges or user interaction, and successful exploitation gains elevated bootloader control.
The record
- CVE
- CVE-2021-0467
- Published
- Jun 14, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1404
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 14, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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