{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2004-0666 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2004-0666 yet. Limit exposure of the affected software until one is available.","what":"CVE-2004-0666 is a high-severity memory corruption vulnerability in n/a, published on 13 Jul 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-0666 and fix it if it is affected.\n\nWhat it is: CVE-2004-0666 is a high-severity memory corruption vulnerability in n/a, published on 13 Jul 2004. 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-2004-0666 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-2004-0666/ (Markdown: https://insights.sbomify.com/CVE-2004-0666/index.md)","id":"CVE-2004-0666","markdown":"https://insights.sbomify.com/CVE-2004-0666/index.md","name":"CVE-2004-0666","record":{"aliases":["GHSA-5p78-xr8q-m3rj"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"POP3 client library","requires_auth":"none","summary":"Remote attackers can crash the application via a buffer overflow in the POP3 client, causing denial of service.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"popclient","vendor":"popclient"}],"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":"Off-by-one error in the POP3_readmsg function in popclient 3.0b6 allows remote attackers to cause a denial of service (application crash) via an e-mail message with a certain line length, which leads to a buffer overflow.","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-2004-0666","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2004"},"n_packages":0,"n_references":5,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2004-0667"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2004-0665"},"products":["n/a"],"published":"2004-07-13","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 crash the application via a buffer overflow in the POP3 client, causing denial of service.","url":"https://insights.sbomify.com/CVE-2004-0666/"}