Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-2398HTTP/2 push headers memory-leak

Description

When an application tells libcurl it wants to allow HTTP/2 server push, and the amount of received headers for the push surpasses the maximum allowed limit (1000), libcurl aborts the server push. When aborting, libcurl inadvertently does not free all the previously allocated headers and instead leaks the memory. Further, this error condition fails silently and is therefore not easily detected by an application.

Timeline

  1. ID reserved

    By curl

  2. · 15 days later

    Published

  3. · 3 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-2398, by who scored it
Scored byCVSSScoreVector
CISA-ADPADP (enrichment)3.1High8.6CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L
NVDNVD · Modified3.1High8.6CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L
EPSS (exploitation in 30 days)
36.1% · top 1.5% of all CVEs (14 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.6.

Affected products

  • curl · curl

    • affected 8.6.0 – ≤ 8.6.0
    • affected 8.5.0 – ≤ 8.5.0
    • affected 8.4.0 – ≤ 8.4.0
    • affected 8.3.0 – ≤ 8.3.0
    • affected 8.2.1 – ≤ 8.2.1
    • affected 8.2.0 – ≤ 8.2.0
    • affected 8.1.2 – ≤ 8.1.2
    • affected 8.1.1 – ≤ 8.1.1
    • affected 8.1.0 – ≤ 8.1.0
    • affected 8.0.1 – ≤ 8.0.1
    • affected 8.0.0 – ≤ 8.0.0
    • affected 7.88.1 – ≤ 7.88.1
    • affected 7.88.0 – ≤ 7.88.0
    • affected 7.87.0 – ≤ 7.87.0
    • affected 7.86.0 – ≤ 7.86.0
    • affected 7.85.0 – ≤ 7.85.0
    • affected 7.84.0 – ≤ 7.84.0
    • affected 7.83.1 – ≤ 7.83.1
    • affected 7.83.0 – ≤ 7.83.0
    • affected 7.82.0 – ≤ 7.82.0
    • affected 7.81.0 – ≤ 7.81.0
    • affected 7.80.0 – ≤ 7.80.0
    • affected 7.79.1 – ≤ 7.79.1
    • affected 7.79.0 – ≤ 7.79.0
    • affected 7.78.0 – ≤ 7.78.0
    • affected 7.77.0 – ≤ 7.77.0
    • affected 7.76.1 – ≤ 7.76.1
    • affected 7.76.0 – ≤ 7.76.0
    • affected 7.75.0 – ≤ 7.75.0
    • affected 7.74.0 – ≤ 7.74.0
    • affected 7.73.0 – ≤ 7.73.0
    • affected 7.72.0 – ≤ 7.72.0
    • affected 7.71.1 – ≤ 7.71.1
    • affected 7.71.0 – ≤ 7.71.0
    • affected 7.70.0 – ≤ 7.70.0
    • affected 7.69.1 – ≤ 7.69.1
    • affected 7.69.0 – ≤ 7.69.0
    • affected 7.68.0 – ≤ 7.68.0
    • affected 7.67.0 – ≤ 7.67.0
    • affected 7.66.0 – ≤ 7.66.0
    • and 37 more

References

References16

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-2398 badge
[![CVE-2024-2398](https://cveledger.app/badge/CVE-2024-2398.svg)](https://cveledger.app/cve/CVE-2024-2398)

Record last updated .