CVE-2024-4437
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-2021-44716. 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 · moderate confidenceThe etcd package in Red Hat OpenStack Platform contains an incomplete fix for CVE-2021-44716, a vulnerability in the Go HTTP/2 implementation. The etcd binary was compiled using the golang.org/x/net/http2 package directly rather than the patched version provided by RHEL's Go distribution, meaning the vulnerable code persists despite RHEL's security updates.
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 package is installedRun 'rpm -qa | grep -i etcd' or 'systemctl list-units | grep etcd' to confirm etcd is present on the systemAffected if etcd package is not installed on the system (not affected)
-
Check installed etcd versionRun 'rpm -q etcd' or 'etcd --version' to retrieve the installed etcd package versionAffected if etcd is installed from Red Hat OpenStack Platform and version falls within affected release ranges
-
Inspect etcd binary for Go http2 library originRun 'rpm -qiv etcd' to check the package build information, specifically looking at build flags or the Go compiler version used; or use 'strings /usr/bin/etcd | grep -i golang.org/x/net/http2' to detect if compiled with the external libraryAffected if The binary was compiled using golang.org/x/net/http2 directly rather than RHEL's patched Go net/http2 (vulnerable)
-
Check for vulnerable HTTP/2 code patternsAnalyze the etcd binary for presence of the specific HTTP/2 vulnerability patterns from CVE-2021-44716; check 'strings' output or use 'rpm -V etcd' to verify package integrityAffected if The binary contains the unpatched HTTP/2 handling code from the original CVE-2021-44716 vulnerability
A system is affected if etcd from Red Hat OpenStack Platform is installed AND the binary was compiled using golang.org/x/net/http2 directly instead of RHEL's patched Go distribution, exposing the CVE-2021-44716 vulnerability in the HTTP/2 implementation.
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 dataRecompile/rebuild the etcd package from source using the updated Go net/http2 library provided by Red Hat Enterprise Linux, then upgrade the package on all affected OpenStack Platform deployments.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-4437 — 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-4437 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