{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2006-5724 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2006-5724 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-5724 is a low-severity memory corruption vulnerability in n/a, published on 4 Nov 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-5724 and fix it if it is affected.\n\nWhat it is: CVE-2006-5724 is a low-severity memory corruption vulnerability in n/a, published on 4 Nov 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-5724 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-5724/ (Markdown: https://insights.sbomify.com/CVE-2006-5724/index.md)","id":"CVE-2006-5724","markdown":"https://insights.sbomify.com/CVE-2006-5724/index.md","name":"CVE-2006-5724","record":{"aliases":["GHSA-hjfj-5586-j3hv"],"analysis":{"component_type":"desktop_application","fix_type":"no_fix_stated","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"ICQ instant messenger","requires_auth":"none","summary":"Local attackers can crash ICQ 2003b by exploiting a heap-based buffer overflow in the Answering Service function via registry values.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"icq","vendor":"mirabilis"}],"cvss":{"score":2.1,"severity":"low","source":"nvd","vector":"AV:L/AC:L/Au:N/C:N/I:N/A:P","version":"2.0"},"cwes":[],"description":"Heap-based buffer overflow the \"Answering Service\" function in ICQ 2003b Build 3916 allows local users to cause a denial of service (application crash) via a long string in the \"AwayMsg Presets\" value in the ICQ\\ICQPro\\DefaultPrefs\\Presets registry key.","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-5724","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2006"},"n_packages":0,"n_references":3,"next":{"headline":"Information disclosure in n/a","id":"CVE-2006-5725"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2006-5723"},"products":["n/a"],"published":"2006-11-04","related":[{"cvss_score":7.8,"headline":"Denial of service in n/a","id":"CVE-2002-2329","kev_date_added":null,"published":"2007-10-26"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2006-4662","kev_date_added":null,"published":"2006-09-09"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2003-0235","kev_date_added":null,"published":"2003-05-07"},{"cvss_score":7.5,"headline":"Integer overflow in n/a","id":"CVE-2003-0236","kev_date_added":null,"published":"2003-05-07"},{"cvss_score":7.5,"headline":"Supply chain in n/a","id":"CVE-2003-0237","kev_date_added":null,"published":"2003-05-07"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2002-0028","kev_date_added":null,"published":"2002-06-25"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-1999-1289","kev_date_added":null,"published":"2001-09-12"}],"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 crash ICQ 2003b by exploiting a heap-based buffer overflow in the Answering Service function via registry values.","url":"https://insights.sbomify.com/CVE-2006-5724/"}