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

> Authenticated users can exploit an SSRF vulnerability in OpenShift Console to perform arbitrary HTTP requests from the server, potentially accessing internal services and disclosing sensitive information.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Nov 2024
- **Updated:** 7 Nov 2025
- **Also known as:** GHSA-v3w7-g6p2-mpx7, GO-2024-3289

## What is CVE-2024-6538?

CVE-2024-6538 is a medium-severity server-side request forgery vulnerability in Red Hat OpenShift Container Platform 4.14, published on 25 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2024-6538?

3 open source packages ship an affected version, including github.com/openshift/console.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/openshift/console` | Go | All versions | None |
| `github.com/openshift/console` | Go | All versions to 6.0.6 | None |
| `github.com/openshift/console` | Go | All versions to 6.0.6 | None |

## How do I fix CVE-2024-6538?

Apply the vendor's patch.

## Is CVE-2024-6538 being exploited?

There is no known exploitation of CVE-2024-6538 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-6538 and fix it if it is affected.

What it is: CVE-2024-6538 is a medium-severity server-side request forgery vulnerability in Red Hat OpenShift Container Platform 4.14, published on 25 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-6538 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/openshift/console (Go): affected all versions; no fix listed
- github.com/openshift/console (Go): affected all versions up to 6.0.6; no fix listed
- github.com/openshift/console (Go): affected all versions up to 6.0.6; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-6538/ (Markdown: https://insights.sbomify.com/CVE-2024-6538/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-6538
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-6538
- OSV: https://osv.dev/vulnerability/CVE-2024-6538

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-6538/
Summaries are generated and may contain mistakes; the official description above is the record.