{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-3638 exists.","fix":"No fix has been published for CVE-2007-3638 yet. Limit exposure of the affected software until one is available.","what":"CVE-2007-3638 is a medium-severity memory corruption vulnerability in n/a, published on 10 Jul 2007. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2007-3638 and fix it if it is affected.\n\nWhat it is: CVE-2007-3638 is a medium-severity memory corruption vulnerability in n/a, published on 10 Jul 2007. Any signed-in user can exploit it over the network, 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-2007-3638 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-2007-3638/ (Markdown: https://insights.sbomify.com/CVE-2007-3638/index.md)","id":"CVE-2007-3638","markdown":"https://insights.sbomify.com/CVE-2007-3638/index.md","name":"CVE-2007-3638","record":{"aliases":["GHSA-7r88-6fh6-rqh5"],"analysis":{"component_type":"desktop_application","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Instant messaging client","requires_auth":"low_privilege","summary":"A buffer overflow in Yahoo! Messenger allows remote attackers with address book access to execute arbitrary code via user-assisted vectors.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"messenger","vendor":"yahoo"}],"cvss":{"score":6,"severity":"medium","source":"nvd","vector":"AV:N/AC:M/Au:S/C:P/I:P/A:P","version":"2.0"},"cwes":[{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"Buffer overflow in Yahoo! Messenger 8.1 allows user-assisted remote authenticated users, who are listed in an address book, to execute arbitrary code via unspecified vectors, aka ZD-00000005.  NOTE: this information is based upon a vague advisory by a vulnerability information sales organization that does not coordinate with vendors or release actionable advisories. A CVE has been assigned for tracking purposes, but duplicates with other CVEs are difficult to determine.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2007-07-16","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2007-07-16","kind":"exploitdb","ref":"30314","stars":null,"title":"Yahoo! Messenger 8.1 - Address Book Remote Buffer Overflow"}],"tier":"weaponised"},"has_fix":null,"headline":"Memory corruption in n/a","id":"CVE-2007-3638","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2007"},"n_packages":0,"n_references":2,"next":{"headline":"Open redirect in n/a","id":"CVE-2007-3639"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2007-3637"},"products":["n/a"],"published":"2007-07-10","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":"CWE Terms of Use","name":"CWE (MITRE)"},{"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-07","vendors":["n/a"]},"summary":"A buffer overflow in Yahoo! Messenger allows remote attackers with address book access to execute arbitrary code via user-assisted vectors.","url":"https://insights.sbomify.com/CVE-2007-3638/"}