CVE-2024-23185 Affecting dovecot23-fts-solr package, versions <2.3.15-150200.65.1


Severity

Recommended
high

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.04% (12th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-SLES156-DOVECOT23FTSSOLR-7887424
  • published4 Sept 2024
  • disclosed3 Sept 2024

Introduced: 3 Sep 2024

CVE-2024-23185  (opens in a new tab)

How to fix?

Upgrade SLES:15.6 dovecot23-fts-solr to version 2.3.15-150200.65.1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream dovecot23-fts-solr package and not the dovecot23-fts-solr package as distributed by SLES. See How to fix? for SLES:15.6 relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1