{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2005-2151 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2005-2151 is a medium-severity memory corruption vulnerability in n/a, published on 6 Jul 2005. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2005-2151 and fix it if it is affected.\n\nWhat it is: CVE-2005-2151 is a medium-severity memory corruption vulnerability in n/a, published on 6 Jul 2005. 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-2005-2151 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-2005-2151/ (Markdown: https://insights.sbomify.com/CVE-2005-2151/index.md)","id":"CVE-2005-2151","markdown":"https://insights.sbomify.com/CVE-2005-2151/index.md","name":"CVE-2005-2151","record":{"aliases":["DEBIAN-CVE-2005-2151","DSA-784-1","GHSA-j458-3qc3-3hff"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Courier Mail Server","requires_auth":"none","summary":"Attackers can cause memory corruption in Courier Mail Server via DNS failures during SPF record lookups, potentially leading to denial of service or code execution.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"courier_mail_server","vendor":"double_precision_incorporated"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:N/I:P/A:N","version":"2.0"},"cwes":[],"description":"spf.c in Courier Mail Server does not properly handle DNS failures when looking up Sender Policy Framework (SPF) records, which could allow attackers to cause memory corruption.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Memory corruption in n/a","id":"CVE-2005-2151","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2005"},"n_packages":0,"n_references":2,"next":{"headline":"SQL injection in n/a","id":"CVE-2005-2152"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2005-2150"},"products":["n/a"],"published":"2005-07-06","related":[{"cvss_score":7.5,"headline":"Auth bypass in n/a","id":"CVE-2005-3532","kev_date_added":null,"published":"2005-12-11"}],"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-07","vendors":["n/a"]},"summary":"Attackers can cause memory corruption in Courier Mail Server via DNS failures during SPF record lookups, potentially leading to denial of service or code execution.","url":"https://insights.sbomify.com/CVE-2005-2151/"}