Device crash via unchecked Bluetooth buffer pulls
Published Sep 13, 2024 · Updated Sep 16, 2024
Heap buffer overflow in Zephyr RTOS 3.6 and earlier allows physically proximate attackers to crash Bluetooth Classic devices. The l2cap_br_info_rsp and sdp_client_receive handlers pull multibyte fields from undersized network buffers without first checking the remaining length. A Bluetooth Classic peer must supply malformed L2CAP information or SDP response data; successful exploitation corrupts heap memory and interrupts the device.
Summary
What happened
Heap buffer overflow in Zephyr RTOS 3.6 and earlier allows physically proximate attackers to crash Bluetooth Classic devices. The l2cap_br_info_rsp and sdp_client_receive handlers pull multibyte fields from undersized network buffers without first checking the remaining length. A Bluetooth Classic peer must supply malformed L2CAP information or SDP response data; successful exploitation corrupts heap memory and interrupts the device.
The record
- CVE
- CVE-2024-6135
- Published
- Sep 13, 2024
- Updated
- Sep 16, 2024
- Vendor
- Zephyr Project
- Product
- Zephyr RTOS
- Classifications
- CWE-122, T1499
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 13, 2024CVE publishedPublication date reported by the CVE source.
- Sep 16, 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=0 <=3.6
- 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.
Public exploit references
- Vendor packet-construction proof of conceptproof of concept · demonstrated
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