Persistent code execution via reboot-reason BCB handling
Published Dec 11, 2023 · Updated Aug 2, 2024
Persistent code execution in Google Android SoC allows remote attackers to compromise Chromecast devices through reboot-reason handling. U-Boot mishandles the reboot reason in the bootloader control block, allowing code execution to persist across device reboots. No privileges or user interaction are required, but exploitation is limited to affected Chromecast with Google TV hardware.
Summary
What happened
Persistent code execution in Google Android SoC allows remote attackers to compromise Chromecast devices through reboot-reason handling. U-Boot mishandles the reboot reason in the bootloader control block, allowing code execution to persist across device reboots. No privileges or user interaction are required, but exploitation is limited to affected Chromecast with Google TV hardware.
The record
- CVE
- CVE-2023-6181
- Published
- Dec 11, 2023
- Updated
- Aug 2, 2024
- Vendor
- Product
- Android
- Classifications
- T1542.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 11, 2023CVE publishedPublication date reported by the CVE source.
- Aug 2, 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 SoC
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
Weakness, pattern, technique
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