Firmware crash via malformed BLE packet
Published Nov 1, 2024 · Updated Nov 4, 2024
Buffer overflow in Cypress Bluetooth SDK 3.66 allows physically proximate attackers to crash BLE device firmware with a crafted packet. The BLE Link Layer trusts a mutated LL_PAUSE_ENC_REQ header length that exceeds the packet's actual size, overflowing a buffer during processing. No authentication or user interaction is required; the crash disconnects the device and normal operation requires a reset.
Summary
What happened
Buffer overflow in Cypress Bluetooth SDK 3.66 allows physically proximate attackers to crash BLE device firmware with a crafted packet. The BLE Link Layer trusts a mutated LL_PAUSE_ENC_REQ header length that exceeds the packet's actual size, overflowing a buffer during processing. No authentication or user interaction is required; the crash disconnects the device and normal operation requires a reset.
The record
- CVE
- CVE-2024-48289
- Published
- Nov 1, 2024
- Updated
- Nov 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120, T1499.004
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 1, 2024CVE publishedPublication date reported by the CVE source.
- Nov 4, 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
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