CVE-2018-15479

An issue was discovered in myStrom WiFi Switch V1 before 2.66, WiFi Switch V2 before 3.80, WiFi Switch EU before 3.80, WiFi Bulb before 2.58, WiFi LED Strip before 3.80, WiFi Button before 2.73, and WiFi Button Plus before 2.73. Devices did not authenticate themselves to the cloud in device to...

CVE-2018-15478

CVE-2018-15478 affects myStrom WiFi Switch and related devices (V1 < 2.66, V2 < 3.80, EU < 3.80, Bulb < 2.58, LED Strip < 3.80, Button < 2.73, Button Plus

Android OS WiFi Broadcast Sensitive Data Exposure

Blog post here: https://wwws.nightwatchcybersecurity.com/2018/08/29/sensitive-data-exposure-via-wifi-broadcasts-in-android-os-cve-2018-9489/ TITLE Sensitive Data Exposure via WiFi Broadcasts in Android OS CVE-2018-9489 SUMMARY System broadcasts by Android OS expose information about the users...

CVE-2018-15479: Improper Authentication

An issue was discovered in myStrom WiFi Switch V1 before 2.66, WiFi Switch V2 before 3.80, WiFi Switch EU before 3.80, WiFi Bulb before 2.58, WiFi LED Strip before 3.80, WiFi Button before 2.73, and WiFi Button Plus before 2.73. Devices did not authenticate themselves to the cloud in device to...

CVE-2018-15478: Improper Authentication

An issue was discovered in myStrom WiFi Switch V1 before 2.66, WiFi Switch V2 before 3.80, WiFi Switch EU before 3.80, WiFi Bulb before 2.58, WiFi LED Strip before 3.80, WiFi Button before 2.73, and WiFi Button Plus before 2.73. The process of registering a device with a cloud account was based o...

KismetMobileDashboard - Mobile UI For Kismet

Prerequisite: git-master level kismet. https://github.com/kismetwireless/kismet 1.Installation. git clone into the kismet git. "/home/whatever/kismet" wiPi@YoMama:/kismet cd /kismet wiPi@YoMama:git clone https://github.com/elkentaro/KismetMobileDashboard.git cd into kismetmobiledashboard sudo mak...

How to Modify or Reallocate Citrix licenses

Reasons for Modify allocation: Allocated licenses to the incorrect host name, host id or MAC address Consolidate multiple license files into one license file Split one license file into multiple license files A problem occurred when adding the license file to the license server...

PVS 7.15.3 The target device detecting the wrong Mac Address

While booting the Target Device, it shows the wrong mac address as 656565656565...

Code injection

A captured MAC/device ID of an iTrack Easy can be registered under multiple user accounts allowing access to getgps GPS data, which can allow unauthenticated parties to track the device...

Design/Logic Flaw

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 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...

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...

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...

CVE-2016-6539 TrackR Bravo MAC address can be exposed in close proximity and used to obtain the device ID

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-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,...

Ridiculously Insecure Smart Lock

Tapplock sells an "unbreakable" Internet-connected lock that you can open with your fingerprint. It turns out that: 1. The lock broadcasts its Bluetooth MAC address in the clear, and you can calculate the unlock key from it. 2. Any Tapplock account an unlock every lock. 3. You can open the lock...