Adjacent code execution via zero-MTU GATT response
Published Jan 21, 2025 · Updated Mar 19, 2025
Out-of-bounds write in Android 12 through 15 allows physically proximate attackers to execute code through a crafted Bluetooth request. build_read_multi_rsp in gatt_sr.cc accepts an MTU of zero and writes a GATT multi-read response without first checking the output bound. No privileges or user interaction are required, but the attacker must be within Bluetooth range; successful exploitation executes code on the device.
Summary
What happened
Out-of-bounds write in Android 12 through 15 allows physically proximate attackers to execute code through a crafted Bluetooth request. build_read_multi_rsp in gatt_sr.cc accepts an MTU of zero and writes a GATT multi-read response without first checking the output bound. No privileges or user interaction are required, but the attacker must be within Bluetooth range; successful exploitation executes code on the device.
The record
- CVE
- CVE-2024-43096
- Published
- Jan 21, 2025
- Updated
- Mar 19, 2025
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-787, T1210
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 21, 2025CVE publishedPublication date reported by the CVE source.
- Mar 19, 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=12
- Affected versionversion=12L
- Affected versionversion=13
- Affected versionversion=14
- Affected versionversion=15
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