Device crash via unchecked null HCI buffer
Published May 24, 2021 · Updated Sep 17, 2024
NULL-pointer dereference in the Bluetooth HCI core of Zephyr RTOS 1.14.2 and 2.2.0 allows attackers to crash devices via send errors. When bt_send returns an error, send_cmd passes a null buffer to hci_cmd_done, which reads buf->pool_id without first checking the pointer. Exploitation depends on influencing a low-level Bluetooth send failure, and the vendor documents only denial of service.
Summary
What happened
NULL-pointer dereference in the Bluetooth HCI core of Zephyr RTOS 1.14.2 and 2.2.0 allows attackers to crash devices via send errors. When bt_send returns an error, send_cmd passes a null buffer to hci_cmd_done, which reads buf->pool_id without first checking the pointer. Exploitation depends on influencing a low-level Bluetooth send failure, and the vendor documents only denial of service.
The record
- CVE
- CVE-2020-10066
- Published
- May 24, 2021
- Updated
- Sep 17, 2024
- Vendor
- Zephyr Project
- Product
- Zephyr RTOS
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 24, 2021CVE publishedPublication date reported by the CVE source.
- Sep 17, 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=v1.14.2 <unspecified
- Affected versionversion=v2.2.0 <unspecified
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