Service interruption via invalid Bluetooth connection parameters
Published May 24, 2021 · Updated Sep 16, 2024
Improper parameter handling in Zephyr RTOS 1.14.2 and 2.2.0 allows physically proximate attackers to interrupt service via Bluetooth. The Bluetooth controller accepts an invalid channel map or hop increment in a CONNECT_IND PDU, so a zero channel count reaches an assertion or division operation. An unauthenticated peer within Bluetooth radio range can trigger an assertion failure or divide-by-zero fault, interrupting the affected device.
Summary
What happened
Improper parameter handling in Zephyr RTOS 1.14.2 and 2.2.0 allows physically proximate attackers to interrupt service via Bluetooth. The Bluetooth controller accepts an invalid channel map or hop increment in a CONNECT_IND PDU, so a zero channel count reaches an assertion or division operation. An unauthenticated peer within Bluetooth radio range can trigger an assertion failure or divide-by-zero fault, interrupting the affected device.
The record
- CVE
- CVE-2020-10069
- Published
- May 24, 2021
- Updated
- Sep 16, 2024
- Vendor
- Zephyr Project
- Product
- Zephyr RTOS
- Classifications
- CWE-233, T1499
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 24, 2021CVE 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=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