Adjacent Bluetooth service interruption via null-pointer dereference
Published Aug 11, 2022 · Updated Aug 3, 2024
Null-pointer dereference in Android 13 Bluetooth allows remote attackers to crash Bluetooth processes through adjacent radio traffic. Google identifies the affected locus only as Bluetooth; it has not published the function, packet field, or dereference path that mishandles the input. A nearby attacker needs no privileges or user interaction, and successful exploitation interrupts Bluetooth service without reported confidentiality or integrity impact.
Summary
What happened
Null-pointer dereference in Android 13 Bluetooth allows remote attackers to crash Bluetooth processes through adjacent radio traffic. Google identifies the affected locus only as Bluetooth; it has not published the function, packet field, or dereference path that mishandles the input. A nearby attacker needs no privileges or user interaction, and successful exploitation interrupts Bluetooth service without reported confidentiality or integrity impact.
The record
- CVE
- CVE-2022-20334
- Published
- Aug 11, 2022
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-476, T1642
- Attack vector
- adjacent
- Privileges
- unauthenticated
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