CVE-2024-23185

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2024-09-10. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2024-20704 (ENISA EUVD) · GHSA-g9m4-c8qf-67qw (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.3%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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 v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation1.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
1.3%
EPSS %ILE
70th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
1.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-11). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 10, 2024

Last Modified

April 15, 2026

Advisory Details (4)

Auto-updated Nov 12, 2026
Patch available.
Web pageMentions a patch (unverified)

[SECURITY] [DLA 3860-1] dovecot security update

https://lists.debian.org/debian-lts-announce/2024/09/msg00002.html
Web page

oss-security - Dovecot CVE-2024-23185: Very large headers can cause resource exhaustion when parsing message

http://www.openwall.com/lists/oss-security/2024/08/15/4
Web page

Full Disclosure: Dovecot CVE-2024-23185: Very large headers can cause resource exhaustion when parsing message

http://seclists.org/fulldisclosure/2024/Aug/18

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntudovecot-submissiond (1:2.3.16+dfsg1-3ubuntu2.4) @ jammy2026-11-12ubuntu
ubuntudovecot-submissiond (1:2.3.21+dfsg1-2ubuntu6) @ noble2026-11-12ubuntu
redhatdovecot-1:2.3.16-6.el8_102024-09-24redhat
redhatdovecot-1:2.3.16-11.el9_4.12024-09-10redhat
redhatdovecot-1:2.3.16-8.el9_2.12024-09-09redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(8 across 8 ecosystems)
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
dovecot—
  • every version up to 2.3.21.1-r0: fixed in 2.3.21.1-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
dovecot—
  • every version up to 2.3.21.1-r0: fixed in 2.3.21.1-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
dovecot—
  • every version up to 2.3.21.1-r0: fixed in 2.3.21.1-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
dovecot—
  • every version up to 2.3.21.1-r0: fixed in 2.3.21.1-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
dovecot1:2.3.13+dfsg1-2, 1:2.3.13+dfsg1-2+deb11u1
  • every version up to 1:2.3.13+dfsg1-2+deb11u2: fixed in 1:2.3.13+dfsg1-2+deb11u2
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
dovecot1:2.3.19.1+dfsg1-2.1
  • every version up to 1:2.3.19.1+dfsg1-2.1+deb12u1: fixed in 1:2.3.19.1+dfsg1-2.1+deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
dovecot—
  • every version up to 1:2.3.21.1+dfsg1-1: fixed in 1:2.3.21.1+dfsg1-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
dovecot—
  • every version up to 1:2.3.21.1+dfsg1-1: fixed in 1:2.3.21.1+dfsg1-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(5)

Data Freshness Timeline

(refreshed 9× in last 7d / 38× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 258 rows on record for this CVE, as 98 entries (2 repeats merged).

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 158 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:46 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  2. 2026-11-12 16:31 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  3. 2026-11-12 06:29 UTCEchelonGraph re-scored
  4. 2026-11-12 06:29 UTCVendor advisory
  5. 2026-11-12 06:29 UTCGHSA enrichmentGHSA-g9m4-c8qf-67qw · GitHub severity HIGH · GitHub CVSS 7.5
  6. 2026-11-11 16:34 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  7. 2026-11-10 16:38 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  8. 2026-11-09 16:31 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  9. 2026-11-08 16:35 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  10. 2026-11-07 16:35 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  11. 2026-11-06 16:31 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  12. 2026-11-05 16:33 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  13. 2026-11-04 21:44 UTCEchelonGraph re-scored
  14. 2026-11-04 21:44 UTCVendor advisory
  15. 2026-11-04 21:44 UTCGHSA enrichmentGHSA-g9m4-c8qf-67qw · GitHub severity HIGH · GitHub CVSS 7.5
  16. 2026-11-04 16:32 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  17. 2026-11-03 16:42 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  18. 2026-11-02 16:40 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  19. 2026-11-01 16:31 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  20. 2026-10-31 16:30 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  21. 2026-10-30 16:31 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  22. 2026-10-29 16:30 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  23. 2026-10-28 16:29 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  24. 2026-10-28 12:58 UTCEchelonGraph re-scored
  25. 2026-10-28 12:58 UTCVendor advisory
Show 73 more
  1. 2026-10-28 12:58 UTCGHSA enrichmentGHSA-g9m4-c8qf-67qw · GitHub severity HIGH · GitHub CVSS 7.5
  2. 2026-10-27 16:29 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  3. 2026-10-26 16:29 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  4. 2026-10-25 17:18 UTCEchelonGraph re-scored
  5. 2026-10-25 16:30 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  6. 2026-10-24 16:30 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  7. 2026-10-23 16:29 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  8. 2026-10-22 16:31 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  9. 2026-10-21 16:29 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  10. 2026-10-20 20:30 UTCEchelonGraph re-scored
  11. 2026-10-20 20:30 UTCVendor advisory
  12. 2026-10-20 20:30 UTCGHSA enrichmentGHSA-g9m4-c8qf-67qw · GitHub severity HIGH · GitHub CVSS 7.5
  13. 2026-10-20 16:30 UTCEPSS rescoreEPSS 1.3% · 69th percentile
  14. 2026-10-19 16:29 UTCEPSS rescoreEPSS 1.3% · 69th percentile
  15. 2026-10-18 16:29 UTCEPSS rescoreEPSS 1.3% · 69th percentile
  16. 2026-10-18 07:26 UTCEchelonGraph re-scored
  17. 2026-10-17 16:30 UTCEPSS rescoreEPSS 1.3% · 69th percentile
  18. 2026-10-16 16:36 UTCEPSS rescoreEPSS 1.3% · 69th percentile
  19. 2026-10-15 16:29 UTCEPSS rescoreEPSS 1.3% · 69th percentile
  20. 2026-10-14 16:30 UTCEPSS rescoreEPSS 1.3% · 69th percentile
  21. 2026-10-13 16:30 UTCEPSS rescoreEPSS 1.3% · 69th percentile
  22. 2026-10-12 18:02 UTCEchelonGraph re-scored
  23. 2026-10-12 16:31 UTCEPSS rescoreEPSS 1.3% · 69th percentile
  24. 2026-10-11 21:27 UTCEchelonGraph re-scored
  25. 2026-10-11 16:20 UTCEchelonGraph re-scored
  26. 2026-10-11 13:45 UTCEPSS rescoreEPSS 1.3% · 69th percentile
  27. 2026-10-10 19:58 UTCEPSS rescoreEPSS 1.3% · 69th percentile
  28. 2026-10-09 20:05 UTCEPSS rescoreEPSS 1.3% · 69th percentile
  29. 2026-10-08 17:07 UTCEPSS rescoreEPSS 1.3% · 69th percentile
  30. 2026-10-07 23:46 UTCEPSS rescoreEPSS 1.3% · 69th percentile
  31. 2026-10-07 08:54 UTCOSV refresh
  32. 2026-10-06 15:15 UTCEPSS rescoreEPSS 1.3% · 69th percentile
  33. 2026-10-05 17:41 UTCEPSS rescoreEPSS 1.3% · 69th percentile
  34. 2026-10-04 23:20 UTCEPSS rescoreEPSS 1.3% · 69th percentile
  35. 2026-10-03 14:23 UTCEPSS rescoreEPSS 1.3% · 69th percentile
  36. 2026-10-01 19:48 UTCEPSS rescoreEPSS 1.3% · 69th percentile
  37. 2026-09-30 16:57 UTCEchelonGraph re-scored
  38. 2026-09-30 15:01 UTCEPSS rescoreEPSS 1.3% · 69th percentile
  39. 2026-09-29 15:17 UTCEPSS rescoreEPSS 1.3% · 69th percentile
  40. 2026-09-28 13:49 UTCEPSS rescoreEPSS 1.3% · 69th percentile
  41. 2026-09-24 14:01 UTCEPSS rescoreEPSS 1.3% · 68th percentile
  42. 2026-09-23 13:46 UTCEPSS rescoreEPSS 1.3% · 68th percentile
  43. 2026-09-20 20:14 UTCEPSS rescoreEPSS 1.3% · 68th percentile
  44. 2026-09-17 14:50 UTCOSV refresh
  45. 2026-09-16 14:06 UTCEPSS rescoreEPSS 1.3% · 68th percentile
  46. 2026-09-16 05:11 UTCEPSS rescoreEPSS 1.3% · 68th percentile
  47. 2026-09-15 03:08 UTCEPSS rescoreEPSS 1.3% · 68th percentile
  48. 2026-09-13 16:45 UTCEPSS rescoreEPSS 1.3% · 68th percentile
  49. 2026-09-12 14:59 UTCEPSS rescoreEPSS 1.3% · 68th percentile
  50. 2026-09-11 14:51 UTCEPSS rescoreEPSS 1.3% · 68th percentile
  51. 2026-09-11 09:34 UTCEPSS rescoreEPSS 1.3% · 68th percentile
  52. 2026-09-08 21:58 UTCEPSS rescoreEPSS 1.3% · 68th percentile
  53. 2026-09-07 15:59 UTCEPSS rescoreEPSS 1.3% · 68th percentile
  54. 2026-09-06 13:46 UTCEPSS rescoreEPSS 1.3% · 68th percentile
  55. 2026-09-05 15:26 UTCEPSS rescoreEPSS 1.3% · 67th percentile
  56. 2026-09-04 13:58 UTCEPSS rescoreEPSS 1.3% · 68th percentile
  57. 2026-09-04 05:05 UTCEPSS rescoreEPSS 1.3% · 68th percentile
  58. 2026-09-02 14:10 UTCEPSS rescoreEPSS 1.3% · 68th percentile
  59. 2026-09-01 13:52 UTCEPSS rescoreEPSS 1.3% · 68th percentile
  60. 2026-08-30 19:15 UTCEPSS rescoreEPSS 1.3% · 68th percentile
  61. 2026-08-30 01:20 UTCEPSS rescoreEPSS 1.3% · 67th percentile
  62. 2026-08-29 15:13 UTCOSV refresh
  63. 2026-08-28 21:39 UTCEPSS rescoreEPSS 1.3% · 67th percentile
  64. 2026-08-27 14:23 UTCEPSS rescoreEPSS 1.3% · 68th percentile
  65. 2026-08-26 14:44 UTCEPSS rescoreEPSS 1.3% · 67th percentile
  66. 2026-08-25 13:47 UTCEPSS rescoreEPSS 1.3% · 67th percentile
  67. 2026-08-23 00:17 UTCEPSS rescoreEPSS 1.3% · 67th percentile
  68. 2026-08-21 23:47 UTCEPSS rescoreEPSS 1.3% · 67th percentile
  69. 2026-08-20 22:53 UTCEPSS rescoreEPSS 1.3% · 67th percentile
  70. 2026-08-19 17:02 UTCEPSS rescoreEPSS 1.3% · 67th percentile
  71. 2026-08-18 13:46 UTCEPSS rescoreEPSS 1.3% · 67th percentile
  72. 2026-08-17 13:45 UTCEPSS rescoreEPSS 1.3% · 67th percentile
  73. 2026-08-16 14:54 UTCEPSS rescoreEPSS 1.3% · 67th percentile

Frequently asked(5)

What is CVE-2024-23185?
CVE-2024-23185 is a high-severity vulnerability; its CVE record was published on 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…
When was the CVE record for CVE-2024-23185 published?
The CVE record for CVE-2024-23185 was published on September 10, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of April 15, 2026; the record at its source may have been updated since.
Is CVE-2024-23185 actively exploited?
CVE-2024-23185 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.3% probability of exploitation in the next 30 days (70th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-23185?
CVE-2024-23185 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2024-23185?
A fix for CVE-2024-23185 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-23185

Explore →

Is Your Infrastructure Affected by CVE-2024-23185?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.