{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2024-28054 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2024-28054 is a high-severity vulnerability in n/a, published on 18 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-28054 and fix it if it is affected.\n\nWhat it is: CVE-2024-28054 is a high-severity vulnerability in n/a, published on 18 Mar 2024. 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-2024-28054 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-2024-28054/ (Markdown: https://insights.sbomify.com/CVE-2024-28054/index.md)","id":"CVE-2024-28054","markdown":"https://insights.sbomify.com/CVE-2024-28054/index.md","name":"CVE-2024-28054","record":{"aliases":["ALPINE-CVE-2024-28054","DEBIAN-CVE-2024-28054","GHSA-5hmm-p9xx-45x3","MGASA-2024-0212","UBUNTU-CVE-2024-28054","USN-6790-1"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Amavis mail filter","requires_auth":"none","summary":"Attackers can bypass malware and banned file checks in Amavis by exploiting MIME boundary interpretation conflicts, allowing malicious content to pass through.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":7.4,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-436","name":"Interpretation Conflict"}],"description":"Amavis before 2.12.3 and 2.13.x before 2.13.1, in part because of its use of MIME-tools, has an Interpretation Conflict (relative to some mail user agents) when there are multiple boundary parameters in a MIME email message. Consequently, there can be an incorrect check for banned files or malware.","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":"Security feature bypass in n/a","id":"CVE-2024-28054","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2024"},"n_packages":0,"n_references":8,"next":{"headline":"AWS Amplify CLI has incorrect trust policy management","id":"CVE-2024-28056"},"packages":[],"prev":{"headline":"Resource Exhaustion via the Invitation Feature","id":"CVE-2024-28053"},"products":["n/a"],"published":"2024-03-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-11-04","vendors":["n/a"]},"summary":"Attackers can bypass malware and banned file checks in Amavis by exploiting MIME boundary interpretation conflicts, allowing malicious content to pass through.","url":"https://insights.sbomify.com/CVE-2024-28054/"}