Device crash via unchecked Bluetooth OTS indication
Published Oct 4, 2024 · Updated Oct 4, 2024
Heap-based buffer overflow in Zephyr RTOS 3.6 and earlier allows physically proximate attackers to crash devices via Bluetooth OTS indications. The olcp_ind_handler function pulls an opcode, request opcode, and result code from a net_buf without confirming that the supplied length covers those bytes. Exploitation requires Bluetooth proximity and use of the OTS client path; a short indication can overrun buffer bounds and destabilize or crash the device.
Summary
What happened
Heap-based buffer overflow in Zephyr RTOS 3.6 and earlier allows physically proximate attackers to crash devices via Bluetooth OTS indications. The olcp_ind_handler function pulls an opcode, request opcode, and result code from a net_buf without confirming that the supplied length covers those bytes. Exploitation requires Bluetooth proximity and use of the OTS client path; a short indication can overrun buffer bounds and destabilize or crash the device.
The record
- CVE
- CVE-2024-6444
- Published
- Oct 4, 2024
- Updated
- Oct 4, 2024
- Vendor
- Zephyr Project
- Product
- Zephyr RTOS
- Classifications
- CWE-787, CWE-122, T1499
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 4, 2024CVE publishedPublication date reported by the CVE source.
- Oct 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=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.
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