Local privilege escalation via missing fastboot lock checks
Published Feb 11, 2022 · Updated Aug 4, 2024
Secure boot bypass in Android SoC fastboot allows local users to gain elevated privileges by booting an unsigned image. The Amlogic U-Boot fastboot command dispatcher fails to require an unlocked bootloader for boot and OEM commands, allowing unsigned images or direct lock-state changes. An attacker needs local fastboot access but no user interaction, and successful exploitation enables arbitrary custom-kernel execution on the affected device.
Summary
What happened
Secure boot bypass in Android SoC fastboot allows local users to gain elevated privileges by booting an unsigned image. The Amlogic U-Boot fastboot command dispatcher fails to require an unlocked bootloader for boot and OEM commands, allowing unsigned images or direct lock-state changes. An attacker needs local fastboot access but no user interaction, and successful exploitation enables arbitrary custom-kernel execution on the affected device.
The record
- CVE
- CVE-2021-39672
- Published
- Feb 11, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1626
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 11, 2022CVE publishedPublication date reported by the CVE source.
- Aug 4, 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
- ADT-3 Secure Boot Bypassfunctional · 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