{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-2665 exists.","fix":"No fix has been published for CVE-2005-2665 yet. Limit exposure of the affected software until one is available.","what":"CVE-2005-2665 is a high-severity memory corruption vulnerability in n/a, published on 23 Aug 2005. 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-2005-2665 and fix it if it is affected.\n\nWhat it is: CVE-2005-2665 is a high-severity memory corruption vulnerability in n/a, published on 23 Aug 2005. 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-2005-2665 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-2005-2665/ (Markdown: https://insights.sbomify.com/CVE-2005-2665/index.md)","id":"CVE-2005-2665","markdown":"https://insights.sbomify.com/CVE-2005-2665/index.md","name":"CVE-2005-2665","record":{"aliases":["GHSA-5mm7-3qq4-v6fr"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Elm mail client","requires_auth":"none","summary":"Remote attackers can execute arbitrary code by sending an email with a long Expires header to users of the Elm mail client.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"elm","vendor":"elm_development_group"}],"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 expires.c in Elm 2.5 PL5 through PL7, and possibly other versions, allows remote attackers to execute arbitrary code via an e-mail message with a long Expires header.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2005-08-22","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2005-08-22","kind":"exploitdb","ref":"1171","stars":null,"title":"Elm \u003c 2.5.8 - Expires Header Remote Buffer Overflow"}],"tier":"weaponised"},"has_fix":null,"headline":"Memory corruption in n/a","id":"CVE-2005-2665","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2005"},"n_packages":0,"n_references":14,"next":{"headline":"Information disclosure in n/a","id":"CVE-2005-2666"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2005-2664"},"products":["n/a"],"published":"2005-08-23","related":[{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2003-0966","kev_date_added":null,"published":"2004-09-01"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2001-1174","kev_date_added":null,"published":"2002-06-25"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-1999-1334","kev_date_added":null,"published":"2001-09-12"},{"cvss_score":6.8,"headline":"Privilege escalation in n/a","id":"CVE-2003-1323","kev_date_added":null,"published":"2007-03-30"},{"cvss_score":4.6,"headline":"Memory corruption in n/a","id":"CVE-1999-1184","kev_date_added":null,"published":"2001-09-12"},{"cvss_score":4.6,"headline":"Path traversal in n/a","id":"CVE-1999-0114","kev_date_added":null,"published":"2000-02-04"}],"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-07","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary code by sending an email with a long Expires header to users of the Elm mail client.","url":"https://insights.sbomify.com/CVE-2005-2665/"}