CVE-2016-6542

The iTrack device tracking ID number, also called "LosserID" in the web API, can be obtained by being in the range of an iTrack device. The tracker ID is the device's BLE MAC address...

CVE-2016-6542 The MAC address/device tracking ID of an iTrack Easy can be obtained within range of the device

The iTrack device tracking ID number, also called "LosserID" in the web API, can be obtained by being in the range of an iTrack device. The tracker ID is the device's BLE MAC address...

CVE-2016-6542

The CVE-2016-6542 entry concerns the iTrack Easy device, where the BLE MAC address (the tracker ID) can be obtained by being within range of the device. The issue is described as an information exposure vulnerability: an unauthenticated party could learn the device’s BLE MAC address, enabling pot...

PT-2018-4943

Name of the Vulnerable Software and Affected Versions iTrack affected versions not specified Description The issue concerns the iTrack device, where the tracking ID number, also referred to as "LosserID" in the web API, can be obtained by being in the range of an iTrack device. The tracker ID is...

CVE-2016-6542: Exposure of Sensitive Information to an Unauthorized Actor

The iTrack device tracking ID number, also called "LosserID" in the web API, can be obtained by being in the range of an iTrack device. The tracker ID is the device's BLE MAC address...

Format string

GIGABYTE BRIX UEFI firmware for the GB-BSi7H-6500 version F6 and GB-BXi7-5775 version F2 platforms does not securely implement BIOSWE, BLE, SMMBWP, and PRx features. As a result, the BIOS is not protected from arbitrary write access and may permit modifications to the SPI flash...

CVE-2017-3197

GIGABYTE BRIX UEFI firmware for the GB-BSi7H-6500 version F6 and GB-BXi7-5775 version F2 platforms does not securely implement BIOSWE, BLE, SMMBWP, and PRx features. As a result, the BIOS is not protected from arbitrary write access and may permit modifications to the SPI flash...

CVE-2017-3197 GIGABYTE BRIX UEFI firmware fails to securely implement BIOS write protection

GIGABYTE BRIX UEFI firmware for the GB-BSi7H-6500 version F6 and GB-BXi7-5775 version F2 platforms does not securely implement BIOSWE, BLE, SMMBWP, and PRx features. As a result, the BIOS is not protected from arbitrary write access and may permit modifications to the SPI flash...

CVE-2017-3197

CVE-2017-3197 concerns GIGABYTE BRIX UEFI firmware for GB-BSi7H-6500 (vF6) and GB-BXi7-5775 (vF2). The root cause is improper implementation of BIOS write-protection features BIOSWE, BLE, SMM_BWP, and PRx, which leaves the BIOS vulnerable to arbitrary writes and possible SPI flash modifications. ...

PT-2018-7246

Name of the Vulnerable Software and Affected Versions: GIGABYTE BRIX UEFI firmware for the GB-BSi7H-6500 version F6 GIGABYTE BRIX UEFI firmware for the GB-BXi7-5775 version F2 Description: The issue concerns the insecure implementation of certain features in the UEFI firmware, specifically BIOSWE...

CVE-2016-6539

The Trackr device ID is constructed of a manufacturer identifier of four zeroes followed by the BLE MAC address in reverse. The MAC address can be obtained by being in close proximity to the Bluetooth device, effectively exposing the device ID. The ID can be used to track devices. Updated apps,...

CVE-2016-6539

The CVE-2016-6539 issue affects the TrackR ecosystem: the device ID is formed by four leading zeroes plus the BLE MAC address reversed, which can be inferred by an attacker in Bluetooth range. This ID exposure enables device tracking. Updated apps (TrackR iOS 5.1.6 and Android 2.2.5) were release...

PT-2018-4940

The Trackr device ID is constructed of a manufacturer identifier of four zeroes followed by the BLE MAC address in reverse. The MAC address can be obtained by being in close proximity to the Bluetooth device, effectively exposing the device ID. The ID can be used to track devices. Updated apps,...

CVE-2016-6539: Exposure of Sensitive Information to an Unauthorized Actor

The Trackr device ID is constructed of a manufacturer identifier of four zeroes followed by the BLE MAC address in reverse. The MAC address can be obtained by being in close proximity to the Bluetooth device, effectively exposing the device ID. The ID can be used to track devices. Updated apps,...

PT-2018-1869

Name of the Vulnerable Software and Affected Versions Texas Instruments BLE-STACK versions 2.2.1 and earlier Description The issue is caused by a buffer overflow in the heap, allowing a remote attacker to gain control of the system by sending specially crafted Bluetooth Low Energy BLE messages...

Totally Pwning the Tapplock (the API way)

An awesome researcher contacted us on the back of our recent Tapplock pwnage. We had been looking at the local BLE unlock mechanism, however he focussed instead on the mobile app API. Vangelis Stykas @evstykas has found a way to unlock any lock, plus scrape users PII and home addresses. Read his...

CVE-2018-11631

Rondaful M1 Wristband Smart Band 1 devices allow remote attackers to send an arbitrary number of call or SMS notifications via crafted Bluetooth Low Energy BLE traffic...

CVE-2018-11631

Technical details about CVE-2018-11631 are not publicly provided in the supplied documents. No concrete information on affected versions, root cause, or fixes is available here. Monitor for updates from official sources.

CVE-2018-10825

CVE-2018-10825 concerns Mimo Baby 2 devices, where BLE communications between the Turtle and Lilypad do not use authentication or encryption. This enables replay or spoofing attacks to inject false baby position and temperature data. The vulnerability description clearly identifies the affected c...

Norton Core Secure WiFi Router - BLE Command Injection (PoC)

Norton Core Secure WiFi Router - BLE Command Injection PoC PoC command injection in BLE service of Norton Core Secure WiFi Router CVE-2018-5234 For more information read paper. To demonstrate the exploitation, we will use: - OS GNU/Linux; - Bluetooth dongle adapter; - BlueZ utility for testing...