dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2024-6538

MEDIUM · 5.3 CVSS v3.1 Published 2024-11-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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
A flaw was found in OpenShift Console. A Server Side Request Forgery (SSRF) attack can happen if an attacker supplies all or part of a URL to the server to query. The server is considered to be in a privileged network position and can often reach exposed services that aren't readily available to clients due to network filtering. Leveraging such an attack vector, the attacker can have an impact on other services and potentially disclose information or have other nefarious effects on the system. The /api/dev-console/proxy/internet endpoint on the OpenShift Console allows authenticated users to have the console's pod perform arbitrary and fully controlled HTTP(s) requests. The full response to these requests is returned by the endpoint. While the name of this endpoint suggests the requests are only bound to the internet, no such checks are in place. An authenticated user can therefore ask the console to perform arbitrary HTTP requests from outside the cluster to a service inside the cluster.

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 confidence

OpenShift Console's /api/dev-console/proxy/internet endpoint allows authenticated users to direct the console pod to make arbitrary HTTP(s) requests. Despite its name implying internet-only access, no validation restricts the destination of these requests, enabling SSRF attacks that can reach internal cluster services from external sources.

MitigationImplement destination validation to ensure requests from /api/dev-console/proxy/internet can only reach internet-accessible endpoints and cannot target internal cluster services. Consider URL allowlisting and network policies as complementary controls.

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

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. Confirm OpenShift Console is deployed
    Run 'oc get deployment console -n openshift-console' or check for the console namespace and pods
    Affected if The console deployment exists in the openshift-console namespace
  2. Verify the proxy endpoint is available
    Check if the route exists: 'oc get route console -n openshift-console' and attempt a GET request to /api/dev-console/proxy/internet (requires authentication)
    Affected if The endpoint responds to authenticated requests (even with 400/500 errors indicates the endpoint exists)
  3. Check for destination validation configuration
    Review console pod environment variables and config maps for any URL allowlisting or destination validation settings: 'oc get deployment console -n openshift-console -o yaml | grep -i valid'
    Affected if No destination validation or URL allowlisting is configured in the console deployment
  4. Inspect network policies restricting console egress
    Run 'oc get networkpolicies -n openshift-console' and check for egress rules that limit the console pod's outbound access to internal cluster services
    Affected if No network policies exist or existing policies allow the console pod to reach internal cluster services on arbitrary ports/protocols

A user is affected if OpenShift Console is deployed with the /api/dev-console/proxy/internet endpoint accessible to authenticated users and no destination validation or network policies are in place to prevent SSRF attacks against internal services.

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

Implement destination validation to ensure requests from /api/dev-console/proxy/internet can only reach internet-accessible endpoints and cannot target internal cluster services. Consider URL allowlisting and network policies as complementary controls.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,670
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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