{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2014-7216 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2014-7216 yet. Limit exposure of the affected software until one is available.","what":"CVE-2014-7216 is a critical memory corruption vulnerability in n/a, published on 11 Sep 2015. 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-2014-7216 and fix it if it is affected.\n\nWhat it is: CVE-2014-7216 is a critical memory corruption vulnerability in n/a, published on 11 Sep 2015. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2014-7216 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-2014-7216/ (Markdown: https://insights.sbomify.com/CVE-2014-7216/index.md)","id":"CVE-2014-7216","markdown":"https://insights.sbomify.com/CVE-2014-7216/index.md","name":"CVE-2014-7216","record":{"aliases":["GHSA-5v9m-r264-24vr"],"analysis":{"component_type":"desktop_application","fix_type":"no_fix_stated","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Yahoo! Messenger","requires_auth":"none","summary":"Remote attackers can cause crashes or execute arbitrary code via malicious emoticons.xml files 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":9.3,"severity":"critical","source":"nvd","vector":"AV:N/AC:M/Au:N/C:C/I:C/A:C","version":"2.0"},"cwes":[{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"Multiple stack-based buffer overflows in Yahoo! Messenger 11.5.0.228 and earlier allow remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via the (1) shortcut or (2) title keys in an emoticons.xml file.","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-2014-7216","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2014"},"n_packages":0,"n_references":6,"next":{"headline":"phpMyAdmin cross-site scripting Vulnerability via ENUM value","id":"CVE-2014-7217"},"packages":[],"prev":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2014-7215"},"products":["n/a"],"published":"2015-09-11","related":[{"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)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["n/a"]},"summary":"Remote attackers can cause crashes or execute arbitrary code via malicious emoticons.xml files in Yahoo! Messenger.","url":"https://insights.sbomify.com/CVE-2014-7216/"}