CVE-2024-12698
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 · uneditedAn incomplete fix for ose-olm-catalogd-container was issued for the Rapid Reset Vulnerability (CVE-2023-39325/CVE-2023-44487) where only unauthenticated streams were protected, not streams created by authenticated sources.
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 confidenceThis is an incomplete fix for the HTTP/2 Rapid Reset vulnerability (CVE-2023-39325/CVE-2023-44487) in the ose-olm-catalogd-container. The initial patch only protected unauthenticated streams, leaving authenticated streams vulnerable to Rapid Reset attacks where an authenticated attacker can reset streams faster than the server can process them, leading to denial of service.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Identify if ose-olm-catalogd-container is deployedRun 'kubectl get pods -A | grep olm-catalogd' or 'podman ps | grep catalogd' to find running catalogd containersAffected if No ose-olm-catalogd-container found means not affected
-
Get the installed container image versionRun 'kubectl get pods -A -o jsonpath="{.items[*].spec.containers[*].image}"' for olm-catalogd, or inspect the container directly with 'podman inspect <container_id>' to retrieve the image tagAffected if Version cannot be determined or is earlier than the complete fix release
-
Verify HTTP/2 protocol is enabled for the serviceCheck the catalogd deployment configuration for HTTP/2 settings: 'kubectl get deployment -A -o jsonpath="{.items[?(@.spec.template.spec.containers[0].name=="catalogd")].spec.template.spec}"' and review any ingress or load balancer settings that may enable HTTP/2Affected if HTTP/2 is enabled and the installed version has the incomplete fix
-
Confirm authentication is configured for the catalogd APIReview the catalogd API configuration for authentication settings: check if RBAC, OLM operator permissions, or API server authentication is enabled for catalogd API accessAffected if Authenticated access to catalogd API is possible and the version has incomplete fix
-
Compare installed version against fixed releaseConsult the Red Hat security advisory for CVE-2024-12698 to obtain the exact version boundary for the complete fix, then compare your installed image version stringAffected if Installed version falls between the incomplete fix and the complete fix release
If ose-olm-catalogd-container is running with HTTP/2 enabled, accepts authenticated requests, and the image version contains the incomplete fix (prior to the complete patch), the environment is affected by this CVE.
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 dataApply the complete fix that protects all HTTP/2 streams, including those created by authenticated sources, by updating to a fully patched version of ose-olm-catalogd-container that addresses the Rapid Reset vulnerability for authenticated streams.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-12698 — 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-12698 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