BLE service deadlock via zero-LLID buffer overwrite
Published Feb 10, 2020 · Updated Aug 5, 2024
Buffer overwrite in BLE stack for NXP KW41Z with Bluetooth Low Energy Driver 2.2.1 and earlier allows physically proximate attackers to deadlock BLE. The receive path accepts an LLID value of zero and overwrites memory adjacent to the packet buffer, leaving the BLE state machine in a malfunctioning deadlock. Exploitation requires radio range and an affected BLE-enabled firmware build; the bounded consequence is interruption of BLE service.
Summary
What happened
Buffer overwrite in BLE stack for NXP KW41Z with Bluetooth Low Energy Driver 2.2.1 and earlier allows physically proximate attackers to deadlock BLE. The receive path accepts an LLID value of zero and overwrites memory adjacent to the packet buffer, leaving the BLE state machine in a malfunctioning deadlock. Exploitation requires radio range and an affected BLE-enabled firmware build; the bounded consequence is interruption of BLE service.
The record
- CVE
- CVE-2019-17060
- Published
- Feb 10, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120, T1499
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 10, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- llid_dealock.pyfunctional · validated
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