{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2006-0670 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2006-0670 is a medium-severity memory corruption vulnerability in n/a, published on 13 Feb 2006. 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-0670 and fix it if it is affected.\n\nWhat it is: CVE-2006-0670 is a medium-severity memory corruption vulnerability in n/a, published on 13 Feb 2006. 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-0670 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-0670/ (Markdown: https://insights.sbomify.com/CVE-2006-0670/index.md)","id":"CVE-2006-0670","markdown":"https://insights.sbomify.com/CVE-2006-0670/index.md","name":"CVE-2006-0670","record":{"aliases":["DSA-990-1","GHSA-fm8c-whcx-jx6x"],"analysis":{"component_type":"other","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Bluetooth packet analyzer","requires_auth":"none","summary":"Remote attackers can crash hcidump via malformed Bluetooth L2CAP packets, requiring a patch to prevent denial of service.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"hcidump","vendor":"bluez_project"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:N/I:N/A:P","version":"2.0"},"cwes":[],"description":"Buffer overflow in l2cap.c in hcidump 1.29 allows remote attackers to cause a denial of service (crash) through a wireless Bluetooth connection via a malformed Logical Link Control and Adaptation Protocol (L2CAP) packet.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Memory corruption in n/a","id":"CVE-2006-0670","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2006"},"n_packages":0,"n_references":13,"next":{"headline":"Memory corruption in n/a","id":"CVE-2006-0671"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2006-0669"},"products":["n/a"],"published":"2006-02-13","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 crash hcidump via malformed Bluetooth L2CAP packets, requiring a patch to prevent denial of service.","url":"https://insights.sbomify.com/CVE-2006-0670/"}