{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2004-0051 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2004-0051 yet. Limit exposure of the affected software until one is available.","what":"CVE-2004-0051 is a high-severity vulnerability in n/a, published on 24 Sep 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-0051 and fix it if it is affected.\n\nWhat it is: CVE-2004-0051 is a high-severity vulnerability in n/a, published on 24 Sep 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-0051 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-0051/ (Markdown: https://insights.sbomify.com/CVE-2004-0051/index.md)","id":"CVE-2004-0051","markdown":"https://insights.sbomify.com/CVE-2004-0051/index.md","name":"CVE-2004-0051","record":{"aliases":["GHSA-p93x-8676-4q6g"],"analysis":{"component_type":"server_software","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Content security gateway","requires_auth":"none","summary":"Remote attackers bypass content restrictions in security gateways by using non-standard MIME encoding values that mail clients interpret differently.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"mailsweeper","vendor":"clearswift"},{"product":"internet_gatekeeper","vendor":"f-secure"},{"product":"ripmime","vendor":"paul_l_daniels"}],"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":"Multiple content security gateway and antivirus products allow remote attackers to bypass content restrictions via MIME messages that use non-standard but frequently supported Content-Transfer-Encoding values such as (1) uuencode, (2) mac-binhex40, and (3) yenc, which may be interpreted differently by mail clients.","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":"Security feature bypass in n/a","id":"CVE-2004-0051","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2004"},"n_packages":0,"n_references":3,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2004-0052"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2004-0050"},"products":["n/a"],"published":"2004-09-24","related":[{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2004-0234","kev_date_added":null,"published":"2004-05-05"},{"cvss_score":7.5,"headline":"Security feature bypass in n/a","id":"CVE-2003-1154","kev_date_added":null,"published":"2005-05-10"},{"cvss_score":7.5,"headline":"Security feature bypass in n/a","id":"CVE-2003-1015","kev_date_added":null,"published":"2004-09-24"},{"cvss_score":7.5,"headline":"Security feature bypass in n/a","id":"CVE-2003-1016","kev_date_added":null,"published":"2004-09-24"},{"cvss_score":7.5,"headline":"Security feature bypass in n/a","id":"CVE-2004-0052","kev_date_added":null,"published":"2004-09-24"},{"cvss_score":7.5,"headline":"Security feature bypass in n/a","id":"CVE-2004-0053","kev_date_added":null,"published":"2004-09-24"}],"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 bypass content restrictions in security gateways by using non-standard MIME encoding values that mail clients interpret differently.","url":"https://insights.sbomify.com/CVE-2004-0051/"}