CVE-2024-23185
Reported by ox · Published September 10, 2024
Very large headers can cause resource exhaustion when parsing message. The message-parser normally reads reasonably sized chunks of the message. However, when it feeds them to message-header-parser, it starts building up "full_value" buffer out of the smaller chunks. The full_value buffer has no size limit, so large headers can cause large memory usage. It doesn't matter whether it's a single long header line, or a single header split into multiple lines. This bug exists in all Dovecot versions. Incoming mails typically have some size limits set by MTA, so even largest possible header size may still fit into Dovecot's vsz_limit. So attackers probably can't DoS a victim user this way. A user could APPEND larger mails though, allowing them to DoS themselves (although maybe cause some memory issues for the backend in general). One can implement restrictions on headers on MTA component preceding Dovecot. No publicly available exploits are known.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| dovecot-devel | Amazon Linux | 1:2.3.20-1.amzn2023.0.2, 1:2.2.36-6.amzn2.1.2 |
| dovecot-pgsql | Amazon Linux | 1:2.3.20-1.amzn2023.0.2, 1:2.2.36-6.amzn2.1.2 |
| dovecot-mysql | Amazon Linux | 1:2.3.20-1.amzn2023.0.2, 1:2.2.36-6.amzn2.1.2 |
| dovecot | Alpine | 2.3.21.1-r0 |
| dovecot-pigeonhole | Amazon Linux | 1:2.3.20-1.amzn2023.0.2, 1:2.2.36-6.amzn2.1.2 |
| dovecot | Amazon Linux | 1:2.3.20-1.amzn2023.0.2, 1:2.2.36-6.amzn2.1.2 |
| ox_dovecot_pro | open-xchange | 2.3.21 |
| OX Dovecot Pro | Open-Xchange GmbH | 2.3.21 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Open-Xchange GmbH | OX Dovecot Pro | 0 |
| amazon:2023 | dovecot-devel | 0 |
| amazon:2 | dovecot-pgsql | 0 |
| amazon:2023 | dovecot-mysql | 0 |
| alpine | dovecot | 0 |
| amazon:2023 | dovecot-pgsql | 0 |
| amazon:2 | dovecot-pigeonhole | 0 |
| amazon:2023 | dovecot-pigeonhole | 0 |
| Open-Xchange GmbH | OX Dovecot Pro | 0 |
| amazon:2 | dovecot | 0 |
| amazon:2023 | dovecot | 0 |
| amazon:2 | dovecot-mysql | 0 |
| open-xchange | ox_dovecot_pro | 0 |
| amazon:2 | dovecot-devel | 0 |
Timeline
- Aug 15, 2024 CVE Published
- Sep 10, 2024 PoC Published
- Sep 11, 2024 EPSS Score (30 in total, the first dated here)
- Oct 4, 2024 Coalition ESS Score (7 in total, the first dated here)
- Jun 2, 2026 Security Advisory (8 in total, the first dated here)
- Sep 17, 2026 Distribution Patch (5 in total, the first dated here)
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2024-23185
vulnetix vdb fixes CVE-2024-23185
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2024-23185/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart