Bluetooth privilege escalation via HTML-rendered device name
Published Dec 15, 2021 · Updated Aug 3, 2024
Improper input validation in the Android Framework on versions 9 through 12 allows remote attackers to gain privileges through Bluetooth pairing. The affected onCreate path renders an unescaped device name as HTML, allowing tags to alter the pairing consent dialog. Exploitation requires Bluetooth proximity and user acceptance of the misleading prompt, after which the malicious device becomes paired.
Summary
What happened
Improper input validation in the Android Framework on versions 9 through 12 allows remote attackers to gain privileges through Bluetooth pairing. The affected onCreate path renders an unescaped device name as HTML, allowing tags to alter the pairing consent dialog. Exploitation requires Bluetooth proximity and user acceptance of the misleading prompt, after which the malicious device becomes paired.
The record
- CVE
- CVE-2021-0933
- Published
- Dec 15, 2021
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-20, CWE-116
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 15, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Android-10 Android-11 Android-12 Android-9
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.
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