CVE-2024-4438
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe etcd package distributed with the Red Hat OpenStack platform has an incomplete fix for CVE-2023-39325/CVE-2023-44487, known as Rapid Reset. 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe etcd package distributed with Red Hat OpenStack platform contains an incomplete fix for the Rapid Reset HTTP/2 vulnerabilities (CVE-2023-39325/CVE-2023-44487). The vulnerability persists because etcd uses golang.org/x/net/http2 instead of the system-provided library from RHEL, and this dependency was not properly updated at compile time with the corrected http2 code that addresses the Rapid Reset attack vector.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify etcd is installedRun 'rpm -qa | grep -i etcd' on RHEL-based systems, or 'etcd --version' to see if the etcd binary exists and is executableAffected if etcd package is installed on the system
-
Check etcd versionExecute 'etcd --version' and note the output. Compare the version string to any available patched versions in your Red Hat errata or consult vendor documentation for fixed releasesAffected if The installed etcd version does not include the patched golang.org/x/net/http2 library
-
Identify http2 library dependencyRun 'etcd --version' and examine the output for version information, or use 'rpm -qi <etcd-package-name>' to get package metadata including dependencies. If accessible, inspect the binary with 'ldd' or check the go.mod in etcd source if availableAffected if etcd was compiled against a vulnerable golang.org/x/net/http2 version that lacks CVE-2023-39325/CVE-2023-44487 fixes
-
Check if HTTP/2 is enabledReview etcd configuration files (typically in /etc/etcd/ or as specified via --http-enabled and related flags) and runtime configuration for HTTP/2 protocol handlingAffected if HTTP/2 support is enabled in etcd, as the Rapid Reset vulnerability exploits the HTTP/2 protocol layer
You are affected if etcd is installed and running with an unpatched golang.org/x/net/http2 dependency that still contains the Rapid Reset vector, regardless of HTTP/2 being explicitly configured.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate the etcd package to a version that incorporates the properly patched golang.org/x/net/http2 library, or rebuild etcd from source ensuring the http2 dependency is updated at compile time with the CVE-2023-39325/CVE-2023-44487 fixes.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-4438 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-4438 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data