CVE-2024-4436
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-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.
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 CVE-2022-41723, a vulnerability in the Go net/http2 library. The root cause is that etcd bundles golang.org/x/net/http2 instead of using the version provided by Red Hat Enterprise Linux, requiring a compile-time update to fully remediate the issue.
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 -q etcd' on RHEL-based systems or check for the etcd binary with 'etcd --version'Affected if etcd package or binary is present on the system
-
Check etcd versionExecute 'etcd --version' and note the server version numberAffected if The installed version predates the complete fix for CVE-2022-41723 in the bundled golang.org/x/net/http2 library
-
Locate bundled http2 library in etcdSearch for 'golang.org/x/net/http2' within the etcd installation directory (typically /usr/libexec/osloient or embedded in the binary); use 'strings etcd | grep golang.org/x/net' or inspect the binaries included with the packageAffected if etcd bundles its own copy of golang.org/x/net/http2 rather than relying on the system-provided version from RHEL
-
Compare against fixed etcd versionContact Red Hat or consult the OpenStack Platform release notes for the version that includes the complete golang.org/x/net/http2 fixAffected if Your installed etcd version is older than the version containing the compile-time fix for CVE-2022-41723
If etcd is installed and bundles its own golang.org/x/net/http2 at a version that predates the complete CVE-2022-41723 fix, the environment is affected by CVE-2024-4436.
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 in Red Hat OpenStack Platform to a version that includes the complete fix, ensuring the compile-time dependency on the corrected golang.org/x/net/http2 library is included.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-4436 — 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-4436 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