# CVE-2024-28054: Security feature bypass in n/a

> Attackers can bypass malware and banned file checks in Amavis by exploiting MIME boundary interpretation conflicts, allowing malicious content to pass through.

- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Mar 2024
- **Updated:** 4 Nov 2025
- **Also known as:** ALPINE-CVE-2024-28054, DEBIAN-CVE-2024-28054, GHSA-5hmm-p9xx-45x3, MGASA-2024-0212, UBUNTU-CVE-2024-28054, USN-6790-1

## What is CVE-2024-28054?

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.

### Official 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.

Weakness: CWE-436 (Interpretation Conflict)

## Which versions are affected by CVE-2024-28054?


## How do I fix CVE-2024-28054?

Upgrade to a fixed version.

## Is CVE-2024-28054 being exploited?

There is no known exploitation of CVE-2024-28054 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-28054 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2024-28054 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-28054/ (Markdown: https://insights.sbomify.com/CVE-2024-28054/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-28054
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-28054
- OSV: https://osv.dev/vulnerability/CVE-2024-28054

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-28054/
Summaries are generated and may contain mistakes; the official description above is the record.