Local information disclosure via missing Bluetooth bounds check
Published Jun 28, 2023 · Updated Dec 4, 2024
Out-of-bounds read in Android 13 Bluetooth handling allows local users with System privileges to disclose process memory without interaction. The btu_ble_proc_ltk_req routine in btu_hcif.cc reads long-term-key request input without a required bounds check, crossing the intended buffer boundary. Exploitation requires local code already running with System privileges; the published record does not identify which memory contents can be exposed.
Summary
What happened
Out-of-bounds read in Android 13 Bluetooth handling allows local users with System privileges to disclose process memory without interaction. The btu_ble_proc_ltk_req routine in btu_hcif.cc reads long-term-key request input without a required bounds check, crossing the intended buffer boundary. Exploitation requires local code already running with System privileges; the published record does not identify which memory contents can be exposed.
The record
- CVE
- CVE-2023-21199
- Published
- Jun 28, 2023
- Updated
- Dec 4, 2024
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-125
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jun 28, 2023CVE publishedPublication date reported by the CVE source.
- Dec 4, 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.
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