{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2006-5611 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2006-5611 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-5611 is a critical vulnerability in n/a, published on 31 Oct 2006. It can only be exploited from the same machine or local network."},"fix_prompt":"Check this codebase for CVE-2006-5611 and fix it if it is affected.\n\nWhat it is: CVE-2006-5611 is a critical vulnerability in n/a, published on 31 Oct 2006. It can only be exploited from the same machine or local network.\nExploitation: There is no known exploitation of CVE-2006-5611 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-5611/ (Markdown: https://insights.sbomify.com/CVE-2006-5611/index.md)","id":"CVE-2006-5611","markdown":"https://insights.sbomify.com/CVE-2006-5611/index.md","name":"CVE-2006-5611","record":{"aliases":["GHSA-pmrr-2wrc-fg62"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["other"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Toshiba Bluetooth Stack","requires_auth":"unknown","summary":"Unspecified vulnerability in Toshiba Bluetooth Stack allows attackers to potentially compromise the system via unknown vectors.","user_interaction":"unknown","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"bluetooth_stack","vendor":"toshiba"}],"cvss":{"score":10,"severity":"critical","source":"nvd","vector":"AV:N/AC:L/Au:N/C:C/I:C/A:C","version":"2.0"},"cwes":[],"description":"Unspecified vulnerability in Toshiba Bluetooth Stack before 4.20.01 has unspecified impact and attack vectors, related to the 4.20.01(T) \"Security fix.\" NOTE: due to the lack of details in the vendor advisory, it is not clear whether this issue is related to CVE-2006-5405.","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":"Other in n/a","id":"CVE-2006-5611","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2006"},"n_packages":0,"n_references":2,"next":{"headline":"Code injection in n/a","id":"CVE-2006-5612"},"packages":[],"prev":{"headline":"Code injection in n/a","id":"CVE-2006-5610"},"products":["n/a"],"published":"2006-10-31","related":[{"cvss_score":6.9,"headline":"Privilege escalation in n/a","id":"CVE-2015-0884","kev_date_added":null,"published":"2015-02-28"},{"cvss_score":5,"headline":"Memory corruption in n/a","id":"CVE-2006-3146","kev_date_added":null,"published":"2006-06-22"},{"cvss_score":5,"headline":"Path traversal in n/a","id":"CVE-2006-0212","kev_date_added":null,"published":"2006-01-14"}],"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":"Unspecified vulnerability in Toshiba Bluetooth Stack allows attackers to potentially compromise the system via unknown vectors.","url":"https://insights.sbomify.com/CVE-2006-5611/"}