{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2014-10374 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2014-10374 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2014-10374 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2014-10374 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2014-10374/ (Markdown: https://insights.sbomify.com/CVE-2014-10374/index.md)","id":"CVE-2014-10374","markdown":"https://insights.sbomify.com/CVE-2014-10374/index.md","name":"CVE-2014-10374","record":{"aliases":["GHSA-mp7v-x8v4-q453"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Fitbit activity tracker","requires_auth":"none","summary":"Attackers can track Fitbit devices across locations using static Bluetooth addresses, violating user privacy without requiring user interaction or special configuration.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"charge_2_firmware","vendor":"fitbit"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"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.","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":"Information disclosure in n/a","id":"CVE-2014-10374","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2014"},"n_packages":0,"n_references":2,"next":{"headline":"Integer overflow in n/a","id":"CVE-2014-10375"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2014-10079"},"products":["n/a"],"published":"2019-07-15","related":[],"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":["n/a"]},"summary":"Attackers can track Fitbit devices across locations using static Bluetooth addresses, violating user privacy without requiring user interaction or special configuration.","url":"https://insights.sbomify.com/CVE-2014-10374/"}