Code execution via oversized Bluetooth inquiry responses
Published Feb 5, 2020 · Updated Aug 4, 2024
Heap-based buffer overflow in the Cypress Wireless IoT Bluetooth codebase allows physically proximate attackers to execute code during inquiry. eir_handleRx retains RFU bits in an EIR length, letting eir_getReceivedEIR copy more than the expected 240 bytes and create a heap write-what-where condition. Exploitation requires repeated short-interval connections from different source addresses while the victim scans for device names.
Summary
What happened
Heap-based buffer overflow in the Cypress Wireless IoT Bluetooth codebase allows physically proximate attackers to execute code during inquiry. eir_handleRx retains RFU bits in an EIR length, letting eir_getReceivedEIR copy more than the expected 240 bytes and create a heap write-what-where condition. Exploitation requires repeated short-interval connections from different source addresses while the victim scans for device names.
The record
- CVE
- CVE-2019-11516
- Published
- Feb 5, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1203
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 5, 2020CVE publishedPublication date reported by the CVE source.
- Aug 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.
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
- Frankenstein CVE-2019-11516 proof of conceptfunctional · 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