{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2006-3146 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2006-3146 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-3146 is a medium-severity memory corruption vulnerability in n/a, published on 22 Jun 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-3146 and fix it if it is affected.\n\nWhat it is: CVE-2006-3146 is a medium-severity memory corruption vulnerability in n/a, published on 22 Jun 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-3146 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-3146/ (Markdown: https://insights.sbomify.com/CVE-2006-3146/index.md)","id":"CVE-2006-3146","markdown":"https://insights.sbomify.com/CVE-2006-3146/index.md","name":"CVE-2006-3146","record":{"aliases":["GHSA-pgpr-c8rx-9p5p"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Toshiba Bluetooth Stack","requires_auth":"none","summary":"Remote attackers can cause a system reboot via a crafted L2CAP echo request in the Toshiba Bluetooth Stack driver.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"bluetooth_stack","vendor":"toshiba"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:N/I:N/A:P","version":"2.0"},"cwes":[{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"The TOSRFBD.SYS driver for Toshiba Bluetooth Stack 4.00.29 and earlier on Windows allows remote attackers to cause a denial of service (reboot) via a L2CAP echo request that triggers an out-of-bounds memory access, similar to \"Ping o' Death\" and as demonstrated by BlueSmack.  NOTE: this issue was originally reported for 4.00.23.","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":"Memory corruption in n/a","id":"CVE-2006-3146","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2006"},"n_packages":0,"n_references":12,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2006-3147"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2006-3145"},"products":["n/a"],"published":"2006-06-22","related":[{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2006-5611","kev_date_added":null,"published":"2006-10-31"},{"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":"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":"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-07","vendors":["n/a"]},"summary":"Remote attackers can cause a system reboot via a crafted L2CAP echo request in the Toshiba Bluetooth Stack driver.","url":"https://insights.sbomify.com/CVE-2006-3146/"}