{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-0399 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2004-0399 is a high-severity memory corruption vulnerability in n/a, published on 12 May 2004. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2004-0399 and fix it if it is affected.\n\nWhat it is: CVE-2004-0399 is a high-severity memory corruption vulnerability in n/a, published on 12 May 2004. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-0399 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-2004-0399/ (Markdown: https://insights.sbomify.com/CVE-2004-0399/index.md)","id":"CVE-2004-0399","markdown":"https://insights.sbomify.com/CVE-2004-0399/index.md","name":"CVE-2004-0399","record":{"aliases":["DEBIAN-CVE-2004-0399","GHSA-rf64-vpcw-m8c6"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service","code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"Exim mail server","requires_auth":"none","summary":"Remote attackers can cause denial of service or execute arbitrary code via a stack-based buffer overflow in Exim when sender verification is enabled.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"exim","vendor":"university_of_cambridge"}],"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":"Stack-based buffer overflow in Exim 3.35, and other versions before 4, when the sender_verify option is true, allows remote attackers to cause a denial of service and possibly execute arbitrary code during sender verification.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2004-05-06","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2004-05-06","kind":"exploitdb","ref":"24093","stars":null,"title":"Exim Sender 3.35 - Verification Remote Stack Buffer Overrun"}],"tier":"weaponised"},"has_fix":true,"headline":"Memory corruption in n/a","id":"CVE-2004-0399","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2004"},"n_packages":0,"n_references":6,"next":{"headline":"Memory corruption in n/a","id":"CVE-2004-0400"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2004-0398"},"products":["n/a"],"published":"2004-05-12","related":[{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2004-0400","kev_date_added":null,"published":"2004-05-12"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2003-0743","kev_date_added":null,"published":"2003-09-06"},{"cvss_score":7.2,"headline":"Memory corruption in n/a","id":"CVE-2005-0021","kev_date_added":null,"published":"2005-01-06"},{"cvss_score":7.2,"headline":"Code injection in n/a","id":"CVE-2002-1381","kev_date_added":null,"published":"2004-09-01"},{"cvss_score":7.2,"headline":"Memory corruption in n/a","id":"CVE-1999-0971","kev_date_added":null,"published":"2000-10-13"},{"cvss_score":4.6,"headline":"Memory corruption in n/a","id":"CVE-2005-0022","kev_date_added":null,"published":"2005-01-06"}],"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 cause denial of service or execute arbitrary code via a stack-based buffer overflow in Exim when sender verification is enabled.","url":"https://insights.sbomify.com/CVE-2004-0399/"}