784 matches found
CVE-2019-5634
CVE-2019-5634 affects Hickory Smart for Android (Belwith)
Apple bleee vulnerability analysis: everyone knows your iPhone on what is happening-vulnerability warning-the black bar safety net
This article describes the Apple BLE Protocol vulnerabilities to cause the Bluetooth information disclosure. Analysis The first analysis of the BLE traffic, unlock the phone and run the BLE sniffer: the python bleadvsearch.py -m 54:69:F1:23:2B:47 54:69:F1:23:2B:47 0e02011a0aff4c0010050b1c0fc556...
Design/Logic Flaw
The Bluetooth Low Energy BLE subsystem on Tapplock devices before 2018-06-12 allows replay attacks...
CVE-2018-20957
CVE-2018-20957 affects Tapplock devices, where the Bluetooth Low Energy (BLE) subsystem before 2018-06-12 is vulnerable to replay attacks. The issue, described across multiple sources (NVD entry and related advisories), indicates an access-control/authentication weakness in the BLE bridge enablin...
CVE-2018-20958
Tapplock’s BLE unlock mechanism before 2018-06-12 relies on Key1 and SerialNo, which are derived from the device’s MAC address that is broadcast publicly. This weak linkage means that credential material used for unlocks is effectively tied to observable hardware identifiers. The Red Hat entry an...
PT-2019-10394
Name of the Vulnerable Software and Affected Versions Tapplock devices versions prior to 2018-06-12 Description The issue concerns the Bluetooth Low Energy BLE subsystem, which relies on Key1 and SerialNo for unlock operations. However, these are derived from the MAC address, which is broadcasted...
Design/Logic Flaw
On Fitbit activity-tracker devices, certain addresses never change. According to the popets-2019-0036.pdf document, this leads to "permanent trackability" and "considerable privacy concerns" without a user-accessible anonymization feature. The devices, such as Charge 2, transmit Bluetooth Low...
CVE-2014-10374: Exposure of Sensitive Information to an Unauthorized Actor
On Fitbit activity-tracker devices, certain addresses never change. According to the popets-2019-0036.pdf document, this leads to "permanent trackability" and "considerable privacy concerns" without a user-accessible anonymization feature. The devices, such as Charge 2, transmit Bluetooth Low...
Hacked Hair Straighteners Can Threaten Homes
Researchers have found a way to successfully hack connected hair straighteners to turn them on and increase the heating element up to its maximum temperature—causing a serious fire hazard for unsuspecting owners. Pen Test Partners decided to put the Glamoriser hair straightener through its securi...
Burning down the house with IoT
For years we’ve been trying to set fire to ‘smart’ things by hacking them. We got some charring on the iKettle, but nothing more. Then we found some smart hair straighteners. The Glamoriser straighteners were promoted heavily on TV at Christmas; they piqued my interest because of the BLE...
Smart Lock Turns Out to be Not So Smart, or Secure
Researchers are warning a keyless smart door lock made by U-tec, called Ultraloq, could allow attackers to track down where the device is being used and easily pick the lock – either virtually or physically. Ultraloq is a Bluetooth fingerprint and touchscreen door lock sold for about $200. It...
How Apple's "Find My" Feature Works
Matthew Green intelligently speculates about how Apple's new "Find My" feature works. If you haven't already been inspired by the description above, let me phrase the question you ought to be asking: how is this system going to avoid being a massive privacy nightmare? Let me count the concerns: I...
CVE-2019-2102
In the Bluetooth Low Energy BLE specification, there is a provided example Long Term Key LTK. If a BLE device were to use this as a hardcoded LTK, it is theoretically possible for a proximate attacker to remotely inject keystrokes on a paired Android host due to improperly used crypto. User...
CVE-2019-2102
CVE-2019-2102 concerns a BLE LTK misconfiguration where a long-term key from the BLE spec example could be used as a hardcoded LTK. The initial description specifies Android as affected, listing Android 7.0 through 9.0, with an attacker in proximity capable of remotely injecting keystrokes on a p...
Smart door lock security who come to tube? Yale and the cover Terman smart locks 0 day vulnerability exposure! - Vulnerability warning-the black bar safety net
With the continuous development of technology, smart home has been popular to people's Lives, Where smart locks product the majority of consumers like. From now on never go out forget to bring the key to the troubles, however the convenience of the smart lock products really safe? Today, the Smar...
Pwning the Nokelock API
Nokelock Vulnerabilities I’ve been talking at some Infosec meet ups about a certain padlock, called the Nokelock. I need to differentiate this right now as there is a product called nokē, this is not about that. This is about a set of Chinese made padlocks called Nokelock from a company called...
Google Titan Security Key Recalled After Bluetooth Pairing Bug
Google is recalling Bluetooth versions of its Titan Security Key after finding a vulnerability that allows attackers in close proximity to take control of the device. Google’s Titan Security Key, launched in the U.S. market last August, is a USB dongle that offers an added layer of security...
Google Will Replace Titan Security Key Over a Bluetooth Flaw
Google will replace any Titan BLE branded security key, after disclosing that a nearby attacker could use it to compromise your accounts...
CVE-2019-2032
In SetScanResponseData of bleadvertiserhciinterface.cc, there is a possible out-of-bound write due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. Product: Android. Version...
PT-2019-16135
Name of the Vulnerable Software and Affected Versions Android versions 8.0 through 9 Description A possible out-of-bound write exists due to a missing bounds check in the SetScanResponseData function of ble advertiser hci interface.cc. This issue could lead to local escalation of privilege withou...