Device crash via zero-length GATT response underflow
Published Mar 29, 2024 · Updated Aug 1, 2024
Buffer over-read in Zephyr RTOS 3.6 and earlier allows physically proximate attackers to crash a Bluetooth LE device with a malformed GATT response. In gatt_find_info_rsp, decrementing a zero response length wraps it to 65,535, causing the descriptor loop to advance beyond the packet and dereference an invalid pointer. The victim must connect to an attacker-controlled Bluetooth LE device and process its response during GATT discovery.
Summary
What happened
Buffer over-read in Zephyr RTOS 3.6 and earlier allows physically proximate attackers to crash a Bluetooth LE device with a malformed GATT response. In gatt_find_info_rsp, decrementing a zero response length wraps it to 65,535, causing the descriptor loop to advance beyond the packet and dereference an invalid pointer. The victim must connect to an attacker-controlled Bluetooth LE device and process its response during GATT discovery.
The record
- CVE
- CVE-2024-3077
- Published
- Mar 29, 2024
- Updated
- Aug 1, 2024
- Vendor
- Zephyr Project
- Product
- Zephyr RTOS
- Classifications
- CWE-126, CWE-190, T1499.004
- Attack vector
- adjacent
- Privileges
- Unavailable
Timeline
How it unfolded
- Mar 29, 2024CVE publishedPublication date reported by the CVE source.
- Aug 1, 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=* <=3.6
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