{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2006-4459 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2006-4459 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-4459 is a high-severity vulnerability in n/a, published on 6 Sep 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-4459 and fix it if it is affected.\n\nWhat it is: CVE-2006-4459 is a high-severity vulnerability in n/a, published on 6 Sep 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-4459 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-4459/ (Markdown: https://insights.sbomify.com/CVE-2006-4459/index.md)","id":"CVE-2006-4459","markdown":"https://insights.sbomify.com/CVE-2006-4459/index.md","name":"CVE-2006-4459","record":{"aliases":["GHSA-w8x9-g86p-x9pf"],"analysis":{"component_type":"hardware_firmware","fix_type":"no_fix_stated","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"AnywhereUSB device","requires_auth":"none","summary":"Local attackers can cause a denial of service crash in AnywhereUSB/5 devices by exploiting an integer overflow in USB string descriptor handling.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"anywhere_usb5","vendor":"digi_international_inc"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"Integer overflow in AnywhereUSB/5 1.80.00 allows local users to cause a denial of service (crash) via a 1 byte header size specified in the USB string descriptor.","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":"Integer overflow in n/a","id":"CVE-2006-4459","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2006"},"n_packages":0,"n_references":5,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2006-4460"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2006-4458"},"products":["n/a"],"published":"2006-09-06","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":"Local attackers can cause a denial of service crash in AnywhereUSB/5 devices by exploiting an integer overflow in USB string descriptor handling.","url":"https://insights.sbomify.com/CVE-2006-4459/"}