{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2001-0700 exists.","fix":"No fix has been published for CVE-2001-0700 yet. Limit exposure of the affected software until one is available.","what":"CVE-2001-0700 is a high-severity memory corruption vulnerability in n/a, published on 9 Mar 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-2001-0700 and fix it if it is affected.\n\nWhat it is: CVE-2001-0700 is a high-severity memory corruption vulnerability in n/a, published on 9 Mar 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-2001-0700 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-2001-0700/ (Markdown: https://insights.sbomify.com/CVE-2001-0700/index.md)","id":"CVE-2001-0700","markdown":"https://insights.sbomify.com/CVE-2001-0700/index.md","name":"CVE-2001-0700","record":{"aliases":["GHSA-w4h5-5xwp-3m26"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"w3m text browser","requires_auth":"none","summary":"Remote attackers can execute arbitrary code by sending a maliciously crafted long base64 encoded MIME header to the w3m text browser.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"w3m","vendor":"w3m"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"Buffer overflow in w3m 0.2.1 and earlier allows a remote attacker to execute arbitrary code via a long base64 encoded MIME header.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2001-06-19","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2001-06-19","kind":"exploitdb","ref":"20941","stars":null,"title":"W3M 0.1/0.2 - Malformed MIME Header Buffer Overflow"}],"tier":"weaponised"},"has_fix":null,"headline":"Memory corruption in n/a","id":"CVE-2001-0700","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2001"},"n_packages":0,"n_references":7,"next":{"headline":"Memory corruption in n/a","id":"CVE-2001-0701"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2001-0699"},"products":["n/a"],"published":"2002-03-09","related":[{"cvss_score":9.3,"headline":"Memory corruption in n/a","id":"CVE-2006-6772","kev_date_added":null,"published":"2006-12-27"},{"cvss_score":6.8,"headline":"Security feature bypass in n/a","id":"CVE-2010-2074","kev_date_added":null,"published":"2010-06-16"},{"cvss_score":5,"headline":"Cross-site scripting in n/a","id":"CVE-2002-1348","kev_date_added":null,"published":"2004-09-01"},{"cvss_score":4.3,"headline":"Cross-site scripting in n/a","id":"CVE-2002-1335","kev_date_added":null,"published":"2002-12-03"}],"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 sending a maliciously crafted long base64 encoded MIME header to the w3m text browser.","url":"https://insights.sbomify.com/CVE-2001-0700/"}