{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2006-6896 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2006-6896 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-6896 is a medium-severity authentication bypass vulnerability in n/a, published on 8 Jan 2007. 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-2006-6896 and fix it if it is affected.\n\nWhat it is: CVE-2006-6896 is a medium-severity authentication bypass vulnerability in n/a, published on 8 Jan 2007. 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-2006-6896 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-2006-6896/ (Markdown: https://insights.sbomify.com/CVE-2006-6896/index.md)","id":"CVE-2006-6896","markdown":"https://insights.sbomify.com/CVE-2006-6896/index.md","name":"CVE-2006-6896","record":{"aliases":["GHSA-q9mj-vpj4-h2ch"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Bluetooth headset","requires_auth":"none","summary":"Remote attackers can bypass pairing restrictions to connect to Plantronics Bluetooth headsets without authorization.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"headset","vendor":"plantronic"}],"cvss":{"score":5.4,"severity":"medium","source":"nvd","vector":"AV:A/AC:M/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"The Bluetooth stack in the Plantronic Headset does not properly implement Non-pairable mode, which allows remote attackers to conduct unauthorized pair-up operations.","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":"Auth bypass in n/a","id":"CVE-2006-6896","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2006"},"n_packages":0,"n_references":3,"next":{"headline":"Path traversal in n/a","id":"CVE-2006-6897"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2006-6895"},"products":["n/a"],"published":"2007-01-08","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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Remote attackers can bypass pairing restrictions to connect to Plantronics Bluetooth headsets without authorization.","url":"https://insights.sbomify.com/CVE-2006-6896/"}