Fitbit Activity Tracker Bluetooth Low Energy PDF Document Anonymity information disclosure

Summaryinfo

A vulnerability identified as problematic has been detected in Fitbit Activity Tracker. The affected element is an unknown function of the component Bluetooth Low Energy. The manipulation as part of PDF Document leads to information disclosure (Anonymity). This vulnerability is referenced as CVE-2014-10374. It is possible to launch the attack on the physical device. No exploit is available.

Detailsinfo

A vulnerability was found in Fitbit Activity Tracker (affected version not known). It has been rated as problematic. This issue affects some unknown functionality of the component Bluetooth Low Energy. The manipulation as part of a PDF Document leads to a information disclosure vulnerability (Anonymity). Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. The summary by CVE is:

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 Energy (BLE) advertising packets with a TxAdd flag indicating random addresses, but the addresses remain constant. If devices come within BLE range at one or more locations where an adversary has set up passive sniffing, the adversary can determine whether the same device has entered one of these locations.

The weakness was published 07/15/2019. The identification of this vulnerability is CVE-2014-10374 since 07/15/2019. An attack has to be approached locally. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• Fitbit

Name

• Activity Tracker

CPE 2.3info

• 🔍

CPE 2.2info

• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion