{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-6539 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-6539 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-6539 is a low-severity vulnerability in TrackR Bravo Mobile Application, published on 6 Jul 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2016-6539 and fix it if it is affected.\n\nWhat it is: CVE-2016-6539 is a low-severity vulnerability in TrackR Bravo Mobile Application, published on 6 Jul 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2016-6539 in the wild and no public exploit code.\n\nAffected product: TrackR Bravo Mobile Application. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2016-6539/ (Markdown: https://insights.sbomify.com/CVE-2016-6539/index.md)","id":"CVE-2016-6539","markdown":"https://insights.sbomify.com/CVE-2016-6539/index.md","name":"CVE-2016-6539","record":{"aliases":["GHSA-3hvh-frvh-wpp7"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"TrackR Bravo mobile app","requires_auth":"none","summary":"An attacker in close proximity can obtain the Bluetooth MAC address to derive the device ID, enabling unauthorized tracking of the TrackR Bravo device.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"certcc","cpe":[{"product":"trackr_firmware","vendor":"thetrackr"}],"cvss":{"score":3.5,"severity":"low","source":"nvd","vector":"CVSS:3.0/AV:A/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"TrackR Bravo MAC address can be exposed in close proximity and used to obtain the device ID","id":"CVE-2016-6539","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2016"},"n_packages":0,"n_references":4,"next":{"headline":"Missing authorization in Bravo Mobile Application","id":"CVE-2016-6540"},"packages":[],"prev":{"headline":"TrackR Bravo mobile application stores account passwords in cleartext","id":"CVE-2016-6538"},"products":["Bravo Mobile Application"],"published":"2018-07-06","related":[{"cvss_score":7.1,"headline":"Denial of service in n/a","id":"CVE-2020-13425","kev_date_added":null,"published":"2020-05-23"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["TrackR"]},"summary":"An attacker in close proximity can obtain the Bluetooth MAC address to derive the device ID, enabling unauthorized tracking of the TrackR Bravo device.","url":"https://insights.sbomify.com/CVE-2016-6539/"}