Device crash via BLE length overflow
Published Feb 12, 2020 · Updated Aug 5, 2024
Buffer overflow in Cypress PSoC 4 BLE component 3.61 and earlier allows physically proximate attackers to crash BLE peripherals. The BLE Link Layer processes data-channel frames whose declared payload exceeds the configured maximum receive size, overflowing memory instead of rejecting them. Radio-range access as a BLE central is sufficient; the demonstrated result is a peripheral hard fault and restart, with no confirmed data compromise.
Summary
What happened
Buffer overflow in Cypress PSoC 4 BLE component 3.61 and earlier allows physically proximate attackers to crash BLE peripherals. The BLE Link Layer processes data-channel frames whose declared payload exceeds the configured maximum receive size, overflowing memory instead of rejecting them. Radio-range access as a BLE central is sufficient; the demonstrated result is a peripheral hard fault and restart, with no confirmed data compromise.
The record
- CVE
- CVE-2019-16336
- Published
- Feb 12, 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 12, 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.
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
- SweynTooth Link Layer Length Overflow demonstrationproof of concept · demonstrated
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