Local privilege escalation via Bluetooth dialog tapjacking
Published Oct 11, 2021 · Updated Aug 3, 2024
Tapjacking in AAOS CarSettings in Google Android Automotive OS 9 and 10 allows local users to enable Bluetooth without consent. Google identifies BluetoothPairingDialog.onCreate as the locus but does not disclose the exact missing overlay check; an overlay redirects the required tap to enable Bluetooth. Exploitation requires user-level code and user interaction on the device; the bounded result is unauthorized Bluetooth activation and local privilege escalation.
Summary
What happened
Tapjacking in AAOS CarSettings in Google Android Automotive OS 9 and 10 allows local users to enable Bluetooth without consent. Google identifies BluetoothPairingDialog.onCreate as the locus but does not disclose the exact missing overlay check; an overlay redirects the required tap to enable Bluetooth. Exploitation requires user-level code and user interaction on the device; the bounded result is unauthorized Bluetooth activation and local privilege escalation.
The record
- CVE
- CVE-2021-0583
- Published
- Oct 11, 2021
- Updated
- Aug 3, 2024
- Vendor
- Product
- Android Automotive OS
- Classifications
- CWE-1021
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 11, 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-9 Android-10
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