{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2001-0070 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2001-0070 yet. Limit exposure of the affected software until one is available.","what":"CVE-2001-0070 is a critical memory corruption vulnerability in n/a, published on 2 Feb 2001. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2001-0070 and fix it if it is affected.\n\nWhat it is: CVE-2001-0070 is a critical memory corruption vulnerability in n/a, published on 2 Feb 2001. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2001-0070 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-2001-0070/ (Markdown: https://insights.sbomify.com/CVE-2001-0070/index.md)","id":"CVE-2001-0070","markdown":"https://insights.sbomify.com/CVE-2001-0070/index.md","name":"CVE-2001-0070","record":{"aliases":["GHSA-9723-j4pc-8jhh"],"analysis":{"component_type":"server_software","fix_type":"no_fix_stated","impacts":["denial_of_service","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Mail server software","requires_auth":"none","summary":"Remote attackers can cause denial of service or execute arbitrary commands via a buffer overflow in the MAIL FROM command.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"1st_up_mail_server","vendor":"upland_solutions"}],"cvss":{"score":10,"severity":"critical","source":"nvd","vector":"AV:N/AC:L/Au:N/C:C/I:C/A:C","version":"2.0"},"cwes":[],"description":"Buffer overflow in 1st Up Mail Server 4.1 allows remote attackers to cause a denial of service, and possibly execute arbitrary commands, via a long MAIL FROM command.","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-2001-0070","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2001"},"n_packages":0,"n_references":3,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2001-0071"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2001-0069"},"products":["n/a"],"published":"2001-02-02","related":[],"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-08","vendors":["n/a"]},"summary":"Remote attackers can cause denial of service or execute arbitrary commands via a buffer overflow in the MAIL FROM command.","url":"https://insights.sbomify.com/CVE-2001-0070/"}