BLE peripheral crash via stale connection dereference
Published Jul 3, 2024 · Updated Aug 1, 2024
NULL pointer dereference in Zephyr RTOS 3.6 and earlier allows physically proximate attackers to crash BLE peripherals with crafted packets. The Bluetooth SMP error path calls bt_conn_send_cb with smp->chan.chan.conn after asynchronous disconnect cleanup has set that connection pointer to NULL. The race requires LE Secure Connections in Just Works mode, a controller without ECC support, and precisely timed DHKey Check and termination packets.
Summary
What happened
NULL pointer dereference in Zephyr RTOS 3.6 and earlier allows physically proximate attackers to crash BLE peripherals with crafted packets. The Bluetooth SMP error path calls bt_conn_send_cb with smp->chan.chan.conn after asynchronous disconnect cleanup has set that connection pointer to NULL. The race requires LE Secure Connections in Just Works mode, a controller without ECC support, and precisely timed DHKey Check and termination packets.
The record
- CVE
- CVE-2024-3332
- Published
- Jul 3, 2024
- Updated
- Aug 1, 2024
- Vendor
- Zephyr Project
- Product
- Zephyr RTOS
- Classifications
- CWE-476, T1499.004
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 3, 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=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