Remote code execution via oversized L2CAP channel request
Published Aug 9, 2022 · Updated Oct 20, 2025
Out-of-bounds write in Android 12 and 12L allows remote attackers to execute code by sending a crafted Bluetooth L2CAP request. l2cble_process_sig_cmd accepts a credit-based connection request declaring more than five channels and writes beyond its fixed channel array. Bluetooth proximity is required, but no authentication, additional privileges, or user interaction is needed.
Summary
What happened
Out-of-bounds write in Android 12 and 12L allows remote attackers to execute code by sending a crafted Bluetooth L2CAP request. l2cble_process_sig_cmd accepts a credit-based connection request declaring more than five channels and writes beyond its fixed channel array. Bluetooth proximity is required, but no authentication, additional privileges, or user interaction is needed.
The record
- CVE
- CVE-2022-20345
- Published
- Aug 9, 2022
- Updated
- Oct 20, 2025
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-77, CWE-787, T1658
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 9, 2022CVE publishedPublication date reported by the CVE source.
- Oct 20, 2025Record 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-12 Android-12L
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