# CVE-2024-4436: Etcd: incomplete fix for cve-2022-41723 in openstack platform

> An incomplete fix in the etcd package allows attackers to cause a denial of service in Red Hat OpenStack Platform.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 May 2024
- **Updated:** 10 Nov 2025
- **Also known as:** GHSA-qghw-hwm7-fw74

## What is CVE-2024-4436?

CVE-2024-4436 is a high-severity denial of service vulnerability in Red Hat OpenStack Platform 16.1, published on 8 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2024-4436?


## How do I fix CVE-2024-4436?

Apply the vendor's patch.

## Is CVE-2024-4436 being exploited?

There is no known exploitation of CVE-2024-4436 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-4436 and fix it if it is affected.

What it is: CVE-2024-4436 is a high-severity denial of service vulnerability in Red Hat OpenStack Platform 16.1, published on 8 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-4436 in the wild and no public exploit code.

Affected product: Red Hat OpenStack Platform 16.1. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-4436/ (Markdown: https://insights.sbomify.com/CVE-2024-4436/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-4436
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-4436
- OSV: https://osv.dev/vulnerability/CVE-2024-4436

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-4436/
Summaries are generated and may contain mistakes; the official description above is the record.