# CVE-2014-10374: Information disclosure in n/a

> Attackers can track Fitbit devices across locations using static Bluetooth addresses, violating user privacy without requiring user interaction or special configuration.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jul 2019
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-mp7v-x8v4-q453

## What is CVE-2014-10374?

CVE-2014-10374 is a medium-severity vulnerability in n/a, published on 15 Jul 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2014-10374?

It affects 1 product.


Products: Fitbit Charge 2 Firmware.

## How do I fix CVE-2014-10374?

No fix has been published for CVE-2014-10374 yet. Limit exposure of the affected software until one is available.

## Is CVE-2014-10374 being exploited?

There is no known exploitation of CVE-2014-10374 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-10374 and fix it if it is affected.

What it is: CVE-2014-10374 is a medium-severity vulnerability in n/a, published on 15 Jul 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-10374 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2014-10374/ (Markdown: https://insights.sbomify.com/CVE-2014-10374/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2014-10374
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2014-10374
- OSV: https://osv.dev/vulnerability/CVE-2014-10374

---
From sbomify Insights: https://insights.sbomify.com/CVE-2014-10374/
Summaries are generated and may contain mistakes; the official description above is the record.