CVE-2024-2398VulnerabilityPublished 20 Aug 2024Updated 5 Nov 2026

Red Hat Security Advisory: curl security update

Affects Red Hat curlSource GCVE Database

Compare

Not known to be exploited.

Data as of 5 Nov 2026, 15:33 UTC

Severity

Medium

Rated by Threat Radar · No CVSS score from NVD or the CNA

Exploitation evidence

Disclosed: evidence found.
CVE published 20 Aug 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

Red Hat has released updated curl packages for Red Hat Enterprise Linux 8 that fix this memory leak vulnerability. Users should apply the security update as described in Red Hat advisory RHSA-2024:5654 and the referenced article https://access.redhat.com/articles/11258 to remediate the issue. No additional mitigation steps are indicated or required beyond applying the official patch.

Description

A memory leak vulnerability exists in the curl utility and libcurl library related to HTTP/2 push headers, identified as CVE-2024-2398. This issue affects Red Hat Enterprise Linux 8 packages of curl. The vulnerability has been rated as moderate severity by Red Hat Product Security. An update addressing this memory leak is available for affected Red Hat Enterprise Linux 8 versions.

Impact

The vulnerability causes a memory leak in curl when handling HTTP/2 push headers. This could lead to increased memory consumption on affected systems, potentially degrading performance or causing resource exhaustion under certain conditions. There is no indication of remote code execution or privilege escalation. The impact is rated moderate by Red Hat.

Summary

CVE-2024-2398 is a memory leak vulnerability in curl's handling of HTTP/2 push headers. The flaw could cause curl to leak memory when processing HTTP/2 push headers, potentially impacting resource usage. Red Hat has issued a security advisory (RHSA-2024:5654) providing updated curl packages for Red Hat Enterprise Linux 8 to fix this issue. The advisory rates the impact as moderate and references the CVE for further details. No CVSS score is provided in the advisory, but the severity is considered medium. No known exploits in the wild have been reported.

CWE-772Missing Release of Resource after Effective Lifetime (opens in a new tab)
Base weaknessLikelihood of exploit: High
The product does not release a resource after its effective lifetime has ended, i.e., after the resource is no longer needed.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation
It is good practice to be responsible for freeing all resources you allocate and to be consistent with how and where you free resources in a function. If you allocate resources that you intend to free upon completion of the function, you must be sure to free the resources at all exit points for that function including…
Operation · Architecture and Design · Resource Limitation
Use resource-limiting settings provided by the operating system or environment. For example, when managing system resources in POSIX, setrlimit() can be used to set limits for certain types of resources, and getrlimit() can determine how many resources are available.
Attack patterns
HTTP DoS (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 5 Nov 2026, 15:33 UTC

WeaknessesCWE-772

Technical details

References

Community reviews

Related threats