# CVE-2024-25584: Other in OX Dovecot Pro

> Dovecot incorrectly splits emails containing specific LF sequences during SMTP relay, allowing attackers to modify message structure.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Sep 2024
- **Updated:** 6 Sep 2024
- **Also known as:** AZL-69869, AZL-69910, GHSA-fx63-vgj4-88r8

## What is CVE-2024-25584?

CVE-2024-25584 is a medium-severity vulnerability in Open-Xchange GmbH OX Dovecot Pro, published on 6 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Dovecot accepts dot LF DOT LF symbol as end of DATA command. RFC requires that it should always be CR LF DOT CR LF. This causes Dovecot to convert single mail with LF DOT LF in middle, into two emails when relaying to SMTP. Dovecot will split mail with LF DOT LF into two mails. Upgrade to latest released version. No publicly available exploits are known.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

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


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

No fix has been published for CVE-2024-25584 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-25584 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-25584 is a medium-severity vulnerability in Open-Xchange GmbH OX Dovecot Pro, published on 6 Sep 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-25584 in the wild and no public exploit code.

Affected product: Open-Xchange GmbH OX Dovecot Pro. 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-25584/ (Markdown: https://insights.sbomify.com/CVE-2024-25584/index.md)
```

## Sources

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

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