Privilege escalation via Bluetooth bounds-check error
Published Aug 11, 2022 · Updated Aug 3, 2024
Out-of-bounds write in Bluetooth in Google Cloud Android 13 allows attackers with System privileges to escalate privileges without interaction. An incorrect bounds check permits Bluetooth code to write beyond the intended buffer, but Google has not disclosed the affected function or input path. Exploitation requires Bluetooth-adjacent access and existing System execution privileges; the bounded result is privilege escalation.
Summary
What happened
Out-of-bounds write in Bluetooth in Google Cloud Android 13 allows attackers with System privileges to escalate privileges without interaction. An incorrect bounds check permits Bluetooth code to write beyond the intended buffer, but Google has not disclosed the affected function or input path. Exploitation requires Bluetooth-adjacent access and existing System execution privileges; the bounded result is privilege escalation.
The record
- CVE
- CVE-2022-20269
- Published
- Aug 11, 2022
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-787, T1068
- Attack vector
- adjacent
- Privileges
- admin
Timeline
How it unfolded
- Aug 11, 2022CVE 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-13
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.
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