{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2002-0146 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2002-0146 yet. Limit exposure of the affected software until one is available.","what":"CVE-2002-0146 is a medium-severity memory corruption vulnerability in n/a, published on 2 Apr 2003. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2002-0146 and fix it if it is affected.\n\nWhat it is: CVE-2002-0146 is a medium-severity memory corruption vulnerability in n/a, published on 2 Apr 2003. 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-2002-0146 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-2002-0146/ (Markdown: https://insights.sbomify.com/CVE-2002-0146/index.md)","id":"CVE-2002-0146","markdown":"https://insights.sbomify.com/CVE-2002-0146/index.md","name":"CVE-2002-0146","record":{"aliases":["GHSA-rg6w-w93w-8gj3"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Email client","requires_auth":"none","summary":"A remote IMAP server can trigger memory corruption in fetchmail via excessive message counts, potentially leading to code execution or denial of service.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"fetchmail","vendor":"fetchmail"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:N/A:N","version":"2.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"fetchmail email client before 5.9.10 does not properly limit the maximum number of messages available, which allows a remote IMAP server to overwrite memory via a message count that exceeds the boundaries of an array.","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-2002-0146","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2002"},"n_packages":0,"n_references":6,"next":{"headline":"Memory corruption in n/a","id":"CVE-2002-0147"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2002-0145"},"products":["n/a"],"published":"2003-04-02","related":[{"cvss_score":10,"headline":"Integer overflow in n/a","id":"CVE-2001-1009","kev_date_added":null,"published":"2002-02-02"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2001-0101","kev_date_added":null,"published":"2001-02-02"},{"cvss_score":7.8,"headline":"Weak cryptography in n/a","id":"CVE-2006-5867","kev_date_added":null,"published":"2007-01-09"},{"cvss_score":7.8,"headline":"Null dereference in n/a","id":"CVE-2006-5974","kev_date_added":null,"published":"2007-01-09"},{"cvss_score":7.8,"headline":"Denial of service in n/a","id":"CVE-2005-4348","kev_date_added":null,"published":"2005-12-21"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2002-1365","kev_date_added":null,"published":"2004-09-01"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2002-1174","kev_date_added":null,"published":"2002-10-01"}],"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"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":"A remote IMAP server can trigger memory corruption in fetchmail via excessive message counts, potentially leading to code execution or denial of service.","url":"https://insights.sbomify.com/CVE-2002-0146/"}