CVE-2019-19194

The Bluetooth Low Energy Secure Manager Protocol SMP implementation on Telink Semiconductor BLE SDK versions before November 2019 for TLSR8x5x through 3.4.0, TLSR823x through 1.3.0, and TLSR826x through 3.3 devices installs a zero long term key LTK if an out-of-order link-layer encryption request...

CVE-2019-19196

The Bluetooth Low Energy Secure Manager Protocol SMP implementation on Telink Semiconductor BLE SDK versions before November 2019 for TLSR8x5x through 3.4.0, TLSR823x through 1.3.0, and TLSR826x through 3.3 devices accepts a pairing request with a key size greater than 16 bytes, allowing an...

Design/Logic Flaw

The Bluetooth Low Energy Secure Manager Protocol SMP implementation on Telink Semiconductor BLE SDK versions before November 2019 for TLSR8x5x through 3.4.0, TLSR823x through 1.3.0, and TLSR826x through 3.3 devices installs a zero long term key LTK if an out-of-order link-layer encryption request...

Buffer overflow

The Bluetooth Low Energy Secure Manager Protocol SMP implementation on Telink Semiconductor BLE SDK versions before November 2019 for TLSR8x5x through 3.4.0, TLSR823x through 1.3.0, and TLSR826x through 3.3 devices accepts a pairing request with a key size greater than 16 bytes, allowing an...

CVE-2019-19194

The Bluetooth Low Energy Secure Manager Protocol SMP implementation on Telink Semiconductor BLE SDK versions before November 2019 for TLSR8x5x through 3.4.0, TLSR823x through 1.3.0, and TLSR826x through 3.3 devices installs a zero long term key LTK if an out-of-order link-layer encryption request...

CVE-2019-19194

The CVE-2019-19194 issue affects Telink Semiconductor BLE SDKs (TLSR8x5x up to 3.4.0; TLSR823x up to 1.3.0; TLSR826x up to 3.3) when Secure Connections pairing is in use. The Bluetooth Low Energy SMP implementation can install a zero long-term key (LTK) if an out-of-order link-layer encryption re...

CVE-2019-19196

The CVE-2019-19196 entry relates to Telink Semiconductor’s BLE SDK SMP implementation. Affected SDKs (before Nov 2019) include TLSR8x5x (up to v3.4.0), TLSR823x (up to v1.3.0), and TLSR826x (up to v3.3). The vulnerability arises when a pairing request with a key size greater than 16 bytes is acce...

CVE-2019-19196

The Bluetooth Low Energy Secure Manager Protocol SMP implementation on Telink Semiconductor BLE SDK versions before November 2019 for TLSR8x5x through 3.4.0, TLSR823x through 1.3.0, and TLSR826x through 3.3 devices accepts a pairing request with a key size greater than 16 bytes, allowing an...

CVE-2019-19194

The Bluetooth Low Energy Secure Manager Protocol SMP implementation on Telink Semiconductor BLE SDK versions before November 2019 for TLSR8x5x through 3.4.0, TLSR823x through 1.3.0, and TLSR826x through 3.3 devices installs a zero long term key LTK if an out-of-order link-layer encryption request...

CVE-2019-19192

The Bluetooth Low Energy implementation on STMicroelectronics BLE Stack through 1.3.1 for STM32WB5x devices does not properly handle consecutive Attribute Protocol ATT requests on reception, allowing attackers in radio range to cause an event deadlock or crash via crafted packets. Recent...

CVE-2019-17060

The Bluetooth Low Energy BLE stack implementation on the NXP KW41Z based on the MCUXpresso SDK with Bluetooth Low Energy Driver 2.2.1 and earlier does not properly restrict the BLE Link Layer header and executes certain memory contents upon receiving a packet with a Link Layer ID LLID equal to...

CVE-2019-17061

The Bluetooth Low Energy BLE stack implementation on Cypress PSoC 4 through 3.62 devices does not properly restrict the BLE Link Layer header and executes certain memory contents upon receiving a packet with a Link Layer ID LLID equal to zero. This allows attackers within radio range to cause...

Cross site request forgery (csrf)

The Bluetooth Low Energy peripheral implementation on Texas Instruments SIMPLELINK-CC2640R2-SDK through 3.30.00.20 and BLE-STACK through 1.5.0 before Q4 2019 for CC2640R2 and CC2540/1 devices does not properly restrict the advertisement connection request packet on reception, allowing attackers i...

Buffer overflow

The Bluetooth Low Energy BLE stack implementation on the NXP KW41Z based on the MCUXpresso SDK with Bluetooth Low Energy Driver 2.2.1 and earlier does not properly restrict the BLE Link Layer header and executes certain memory contents upon receiving a packet with a Link Layer ID LLID equal to...

Buffer overflow

The Bluetooth Low Energy BLE stack implementation on Cypress PSoC 4 through 3.62 devices does not properly restrict the BLE Link Layer header and executes certain memory contents upon receiving a packet with a Link Layer ID LLID equal to zero. This allows attackers within radio range to cause...

CVE-2017-18642

CVE-2017-18642 affects Syska Smart Bulb devices up to 2017-08-06, where RGB parameters are transmitted over cleartext Bluetooth Low Energy (BLE). The underlying issue is unencrypted BLE traffic, enabling sniffing, reverse engineering, and replay attacks. Connected sources corroborate the BLE clea...

CVE-2019-19193

CVE-2019-19193 affects TI Bluetooth Low Energy peripheral in SIMPLELINK-CC2640R2-SDK (up to 3.30.00.20) and BLE-STACK (up to 1.5.0) for CC2640R2 and CC2540/1. The issue is that the advertisement connection request packet is not properly restricted on reception, allowing attackers in radio range t...

CVE-2019-17061

The CVE-2019-17061 entry concerns the Bluetooth Low Energy (BLE) stack in Cypress PSoC 4 devices (up to version 3.62). The issue is that the BLE Link Layer header is not properly restricted when processing a packet with LLID = 0, allowing an attacker in radio range to trigger a deadlock, anomalou...

CVE-2019-17060

The Bluetooth Low Energy BLE stack implementation on the NXP KW41Z based on the MCUXpresso SDK with Bluetooth Low Energy Driver 2.2.1 and earlier does not properly restrict the BLE Link Layer header and executes certain memory contents upon receiving a packet with a Link Layer ID LLID equal to...

CVE-2019-17060

The CVE-2019-17060 entry affects the NXP KW41Z BLE stack (MCUXpresso SDK Bluetooth Low Energy Driver 2.2.1 and earlier). The vulnerability arises because the Link Layer header is not properly restricted when LLID = 0, causing the device to execute certain memory contents upon frame reception. Con...