Fitbit Charge 2
Approved changes feed: RSS · Atom
cpe:2.3:h:fitbit:charge_2:-:*:*:*:*:*:*:*
part: h version: - update: *
| Vendor | Fitbit (9a44c9e5-1c66-5bff-95fa-8dce40161b74) |
|---|---|
| Product | Charge 2 (ae7d4354-f2e3-5e7d-ac74-0d7993e6f9e8) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2014-10374 |
not_vulnerable | 2026-06-08 05:05:15.642652 |
Details available
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.
Published: 2019-07-15T12:47:25.000Z
Updated: 2024-08-06T14:02:38.299Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.