CVE-2024-4436VulnerabilityPublished 8 May 2024Updated 10 Nov 2025

CVE-2024-4436: Uncontrolled Resource Consumption

Source CVE Database V5

Mentioned vulnerabilities

CVE-2022-41723

Not known to be exploited · CVSS 7.5 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.7% chance of exploitation in 30 days – higher than 55% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 8 May 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 2026-10-25.

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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC 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

To mitigate CVE-2024-4436, organizations should: 1) Identify all Red Hat OpenStack deployments using the affected etcd package. 2) Recompile or update the etcd package to link against the patched http2 package provided by Red Hat Enterprise Linux, ensuring the fix for CVE-2022-41723 is fully applied. 3) Apply all relevant Red Hat security advisories and updates promptly. 4) Restrict network access to etcd endpoints, limiting exposure to trusted management networks and using firewall rules or security groups to reduce attack surface. 5) Monitor etcd service metrics and logs for unusual resource consumption patterns that could indicate exploitation attempts. 6) Implement rate limiting or traffic filtering at the network perimeter to mitigate potential HTTP/2 abuse. 7) Consider deploying intrusion detection/prevention systems tuned to detect anomalous HTTP/2 traffic targeting etcd. These steps go beyond generic advice by focusing on the specific cause—incorrect http2 package usage—and emphasizing recompilation and network-level protections.

Description

The etcd package distributed with the Red Hat OpenStack platform has an incomplete fix for CVE-2022-41723. This issue occurs because the etcd package in the Red Hat OpenStack platform is using http://golang.org/x/net/http2 instead of the one provided by Red Hat Enterprise Linux versions, meaning it should be updated at compile time instead.

Impact

The primary impact of CVE-2024-4436 is on the availability of the etcd service within Red Hat OpenStack deployments. Since etcd is a critical component for storing configuration data and coordinating distributed systems, its unavailability can lead to partial or complete disruption of OpenStack cloud services. This can affect cloud management, orchestration, and any applications relying on OpenStack infrastructure. Organizations worldwide that depend on Red Hat OpenStack for private or public cloud environments may experience service outages, degraded performance, or instability. The vulnerability does not impact confidentiality or integrity directly but can cause denial of service conditions that disrupt business operations, potentially leading to financial losses and reputational damage. Given the remote and unauthenticated nature of the exploit, threat actors could launch attacks at scale, targeting cloud providers or enterprises with exposed OpenStack management interfaces. The lack of known exploits in the wild currently reduces immediate risk but does not eliminate the potential for future exploitation.

References

Community reviews

Loading reviews…