LiveActive security incident?Get immediate response
CVE Record

CVE-2014-10374: On Fitbit activity-tracker devices, certain addresses never change.

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Some Fitbit trackers advertise a Bluetooth identifier that appears random but does not change. A passive observer within Bluetooth Low Energy range can recognize the same device across locations. The main risk is privacy and physical-location tracking, not system compromise.

Executive priority

Treat this as a privacy and location-tracking risk. It is most urgent where wearable use could reveal presence at sensitive sites or regulated environments. Business response should focus on policy, vendor guidance, and risk acceptance.

Technical view

CVE-2014-10374 describes Fitbit activity trackers, including Charge 2 examples, sending BLE advertising packets with TxAdd indicating random addresses while those addresses remain constant. Sources state this enables permanent trackability and has no user-accessible anonymization feature. Affected product/version metadata is incomplete.

Likely exposure

Exposure is likely for organizations or individuals using implicated Fitbit activity trackers in places where passive BLE monitoring could occur, especially sensitive facilities, workplaces, clinics, or recurring personal locations. The CVE record does not provide complete affected version data.

Exploitation context

No active exploitation is stated in the supplied sources, and the CVE is not KEV-listed. The described scenario requires passive BLE observation within range at one or more monitored locations to correlate the same device over time.

Researcher notes

The evidence is limited to the CVE description and cited PETS paper. Affected version ranges, CVSS, CWE, and vendor remediation details are not supplied. Avoid assuming all Fitbit models are affected beyond the cited evidence.

Mitigation direction

  • Check Fitbit or vendor guidance for firmware updates, advisories, or privacy controls.
  • Restrict affected trackers in sensitive locations where persistent identifiers create unacceptable privacy risk.
  • Update privacy risk assessments for wearable BLE devices used by employees or visitors.
  • Consider replacement devices only if vendor guidance confirms improved address rotation.

Validation and detection

  • Inventory Fitbit activity trackers used in sensitive or monitored environments.
  • Compare device models against the CVE record and cited PETS paper examples.
  • Review whether vendor firmware guidance addresses BLE address rotation or anonymization.
  • Validate organizational privacy controls for BLE wearables without collecting unnecessary personal data.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2014-10374 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.