{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2006-6584 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2006-6584 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-6584 is a critical memory corruption vulnerability in n/a, published on 15 Dec 2006. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2006-6584 and fix it if it is affected.\n\nWhat it is: CVE-2006-6584 is a critical memory corruption vulnerability in n/a, published on 15 Dec 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2006-6584 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-6584/ (Markdown: https://insights.sbomify.com/CVE-2006-6584/index.md)","id":"CVE-2006-6584","markdown":"https://insights.sbomify.com/CVE-2006-6584/index.md","name":"CVE-2006-6584","record":{"aliases":["GHSA-p34v-p234-wj5h"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Italk+ VoIP client","requires_auth":"none","summary":"Remote attackers can trigger buffer overflows in Italk+ to crash the application or execute arbitrary code.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"italkplus","vendor":"italkplus"}],"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":"Multiple buffer overflows in italkplus (Italk+) before 0.92.1 allow remote attackers to cause a denial of service (application crash) and possibly execute arbitrary code via unspecified vectors.","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-6584","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2006"},"n_packages":0,"n_references":4,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2006-6585"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2006-6583"},"products":["n/a"],"published":"2006-12-15","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 trigger buffer overflows in Italk+ to crash the application or execute arbitrary code.","url":"https://insights.sbomify.com/CVE-2006-6584/"}