dbcve.org
Openshift Container PlatformApplication · Redhat

CVE-2024-50311

MEDIUM · 6.5 CVSS v3.1 Published 2024-10-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
A denial of service (DoS) vulnerability was found in OpenShift. This flaw allows attackers to exploit the GraphQL batching functionality. The vulnerability arises when multiple queries can be sent within a single request, enabling an attacker to submit a request containing thousands of aliases in one query. This issue causes excessive resource consumption, leading to application unavailability for legitimate users.

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

OpenShift contains a DoS vulnerability in its GraphQL API where the batching functionality allows unlimited aliases within a single query. Attackers can submit requests containing thousands of aliases, causing excessive CPU and memory consumption that renders the application unavailable to legitimate users.

MitigationApply the available OpenShift security update to restrict the number of GraphQL aliases per request, and implement query complexity analysis and rate limiting on the GraphQL endpoint as a defense-in-depth measure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Openshift Container PlatformApplication
Affected:= 4.0

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 checks

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

  1. Check OpenShift Container Platform version
    Run 'oc get clusterversion' or check the cluster version in the OpenShift web console under Administration > Cluster Settings
    Affected if The installed version is 4.0 (exact match as specified in affected products)
  2. Identify GraphQL API endpoint exposure
    Check if the OpenShift GraphQL API (often at /graphql or /apis/graphql) is externally accessible by reviewing route configurations: 'oc get routes --all-namespaces' or ingress controller settings
    Affected if The GraphQL endpoint is exposed and reachable from network locations where attackers could submit requests
  3. Verify batching functionality is enabled
    Review GraphQL server configuration for batch queries and alias support. Check if the GraphQL schema allows multiple aliases in a single query by inspecting the API endpoint configuration or documentation
    Affected if GraphQL batching and aliasing are enabled without limits on the number of aliases per request
  4. Check for existing query complexity limits
    Inspect any existing GraphQL protection mechanisms such as query depth limits, alias count restrictions, or rate limiting configuration in the API gateway or GraphQL server settings
    Affected if No alias count limits or rate limiting are configured on the GraphQL endpoint, allowing unlimited aliases per request
  5. Monitor for anomalous GraphQL request patterns
    Review API request logs or metrics for GraphQL endpoints, looking for queries with unusually high alias counts or batch sizes that could indicate exploitation attempts
    Affected if Current monitoring shows or historical logs reveal requests with thousands of aliases, indicating active exploitation or vulnerability probing

A user is affected if running OpenShift Container Platform version 4.0 with an exposed GraphQL endpoint that lacks alias count limits and query complexity controls.

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

Apply the available OpenShift security update to restrict the number of GraphQL aliases per request, and implement query complexity analysis and rate limiting on the GraphQL endpoint as a defense-in-depth measure.

Fix this in Openshift Container Platform Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-50311 — 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-2024-50311 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