Physical root access via unlocked U-Boot console
Published Mar 20, 2020 · Updated Aug 5, 2024
Missing bootloader authentication in homee Brain Cube V2 through 2.23.0 allows physically proximate attackers to gain root access. The exposed internal UART reaches an unlocked U-Boot console that accepts an init=/bin/sh kernel parameter without authentication. Opening the device and attaching a UART adapter is required; the resulting root shell can read credentials or modify any device data.
Summary
What happened
Missing bootloader authentication in homee Brain Cube V2 through 2.23.0 allows physically proximate attackers to gain root access. The exposed internal UART reaches an unlocked U-Boot console that accepts an init=/bin/sh kernel parameter without authentication. Opening the device and attaching a UART adapter is required; the resulting root shell can read credentials or modify any device data.
The record
- CVE
- CVE-2019-16258
- Published
- Mar 20, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-306, T1068
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 20, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 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.
Weakness, pattern, technique
Public exploit references
- SySS UART-to-U-Boot root-shell proof of conceptproof of concept · 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