CVE-2016-6539 json
TrackR Bravo MAC address can be exposed in close proximity and used to obtain the device ID
published 2018-07-06 8 y ago modified 2026-06-17 4 mo ago also EUVD-2016-7460
- cvss
- 3.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 70%
- public exploits
- 0
- none known
Summary
The Trackr device ID is constructed of a manufacturer identifier of four zeroes followed by the BLE MAC address in reverse. The MAC address can be obtained by being in close proximity to the Bluetooth device, effectively exposing the device ID. The ID can be used to track devices. Updated apps, version 5.1.6 for iOS and 2.2.5 for Android, have been released by the vendor to address the vulnerabilities in CVE-2016-6538, CVE-2016-6539, CVE-2016-6540 and CVE-2016-6541.
Patch / fix
- thetrackr trackr_firmware 2.2.5, 5.1.6
Exploit prediction
1.29% chance of exploitation in the next 30 days, higher than 70% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- blog.rapid7.com https://blog.rapid7.com/2016/10/25/multiple-bluetooth-low-energy-ble-tracker-vulnerabilities/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 3.5 | CVSS:3.0/AV:A/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N |
| NVD | 2.0 | 3.3 | AV:A/AC:L/Au:N/C:P/I:N/A:N |
Affected products
- TrackR Bravo Mobile Application
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
blog.rapid7.com
/2016/10/25/multiple-bluetooth-low-energy-ble-tracker-vulnerabilities/
exploit, technical-description, third-party-advisory
-
securityfocus.com
/bid/93874
vdb-entry, third-party-advisory
-
kb.cert.org
/vuls/id/TNOY-AF3KCZ
third-party-advisory, us-government-resource
-
kb.cert.org
/vuls/id/617567
third-party-advisory, us-government-resource
Sources
- CVE List CVE-2016-6539
- NVD CVE-2016-6539
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.