dbcve.org
Uncontrolled Resource ConsumptionWeakness · CWE-400

CVE-2023-6596

HIGH · 7.5 CVSS v3.1 Published 2024-04-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
An incomplete fix was shipped for the Rapid Reset (CVE-2023-44487/CVE-2023-39325) vulnerability for an OpenShift Containers.

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 confidence

This CVE addresses an incomplete fix for the Rapid Reset vulnerability (CVE-2023-44487/CVE-2023-39325) in OpenShift Containers. The Rapid Reset attack exploits HTTP/2 stream cancellation via RST_STREAM frames to cause denial of service. The original patches were insufficient, leaving OpenShift deployments vulnerable to variant attacks.

MitigationOrganizations running affected OpenShift Container Platform versions should apply the complete vendor-supplied patch for CVE-2023-6596, which supersedes the prior Rapid Reset fixes, and validate that HTTP/2 stream management is properly secured.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify OpenShift Container Platform version
    Run 'oc get clusterversion version -o jsonpath='{.spec.channel}' && oc get clusterversion version -o jsonpath='{.status.desired.version}' or check /etc/os-release for OCP version
    Affected if Version falls within the range that was patched incompletely for CVE-2023-44487/CVE-2023-39325 (contact Red Hat for exact affected version ranges)
  2. Verify HTTP/2 protocol is enabled
    Check ingress controller and router configuration: 'oc get ingresscontroller default -n openshift-ingress-operator -o yaml' and inspect spec.http2.enabled or router configuration for HTTP/2 settings
    Affected if HTTP/2 is explicitly enabled in ingress/router configuration (vulnerability only applies when HTTP/2 is active)
  3. Confirm patch applied status
    Check cluster for installed updates related to HTTP/2 stream handling: 'oc get clusterversion version -o jsonpath='{.status.history}' or check operator history for networking components
    Affected if No update containing the complete CVE-2023-6596 fix is listed in the cluster update history, or update history shows the original incomplete fix only

Environment is affected if running an OpenShift version that originally received CVE-2023-44487/CVE-2023-39325 patches but has not yet received the complete CVE-2023-6596 patch, AND HTTP/2 is enabled in the ingress/router configuration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Organizations running affected OpenShift Container Platform versions should apply the complete vendor-supplied patch for CVE-2023-6596, which supersedes the prior Rapid Reset fixes, and validate that HTTP/2 stream management is properly secured.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-6596 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-6596 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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