{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2002-0031 exists.","fix":"No fix has been published for CVE-2002-0031 yet. Limit exposure of the affected software until one is available.","what":"CVE-2002-0031 is a medium-severity memory corruption vulnerability in n/a, published on 11 Jun 2002. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2002-0031 and fix it if it is affected.\n\nWhat it is: CVE-2002-0031 is a medium-severity memory corruption vulnerability in n/a, published on 11 Jun 2002. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2002-0031 exists.\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-2002-0031/ (Markdown: https://insights.sbomify.com/CVE-2002-0031/index.md)","id":"CVE-2002-0031","markdown":"https://insights.sbomify.com/CVE-2002-0031/index.md","name":"CVE-2002-0031","record":{"aliases":["GHSA-h292-wpw4-4xhf"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Yahoo Messenger client","requires_auth":"none","summary":"Remote attackers can execute arbitrary code by tricking users into opening malicious ymsgr URIs in Yahoo Messenger.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"messenger","vendor":"yahoo"}],"cvss":{"score":4.6,"severity":"medium","source":"nvd","vector":"AV:L/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"Buffer overflows in Yahoo! Messenger 5,0,0,1064 and earlier allows remote attackers to execute arbitrary code via a ymsgr URI with long arguments to (1) call, (2) sendim, (3) getimv, (4) chat, (5) addview, or (6) addfriend.","ecosystems":[],"exploits":{"exploitdb":2,"first_seen":"2002-05-27","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2002-05-27","kind":"exploitdb","ref":"21484","stars":null,"title":"Yahoo! Messenger 5.0 - Call Center Buffer Overflow"},{"date":"2003-06-23","kind":"exploitdb","ref":"45","stars":null,"title":"Yahoo Messenger 5.5 - 'DSR-ducky.c' Remote Overflow"}],"tier":"weaponised"},"has_fix":null,"headline":"Memory corruption in n/a","id":"CVE-2002-0031","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2002"},"n_packages":0,"n_references":4,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2002-0032"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2002-0030"},"products":["n/a"],"published":"2002-06-11","related":[{"cvss_score":9.3,"headline":"Memory corruption in n/a","id":"CVE-2014-7216","kev_date_added":null,"published":"2015-09-11"},{"cvss_score":9.3,"headline":"Memory corruption in n/a","id":"CVE-2007-4515","kev_date_added":null,"published":"2007-08-31"},{"cvss_score":9.3,"headline":"Memory corruption in n/a","id":"CVE-2007-4391","kev_date_added":null,"published":"2007-08-17"},{"cvss_score":9.3,"headline":"Memory corruption in n/a","id":"CVE-2007-3147","kev_date_added":null,"published":"2007-06-11"},{"cvss_score":9.3,"headline":"Memory corruption in n/a","id":"CVE-2007-3148","kev_date_added":null,"published":"2007-06-11"},{"cvss_score":9.3,"headline":"Memory corruption in n/a","id":"CVE-2007-1680","kev_date_added":null,"published":"2007-04-06"},{"cvss_score":9.3,"headline":"Memory corruption in n/a","id":"CVE-2006-6603","kev_date_added":null,"published":"2006-12-15"}],"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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-08","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary code by tricking users into opening malicious ymsgr URIs in Yahoo Messenger.","url":"https://insights.sbomify.com/CVE-2002-0031/"}