CVE-2024-6538 — console
MEDIUMCVE-2024-6538 is a medium-severity (CVSS 5.3) Server-Side Request Forgery (SSRF) vulnerability in github.com/openshift/console. No vendor fix is recorded yet; mitigation options are listed below.
Openshift-console: openshift console: server-side request forgery
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-6538.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2024-6538 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,156 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
github.com/openshift/consoleReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/openshift/console | all versions | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/openshift/console, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of github.com/openshift/console has shipped for CVE-2024-6538 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2024-6538 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2024-6538. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat OpenShift Container Platform 4.16 | openshift4/ose-console-rhel9:v4.16.0-202506020836.p0.g94ae640.assembly.stream.el9 | RHSA-2025:8556 |
| Red Hat OpenShift Container Platform 4.17 | openshift4/ose-console-rhel9:v4.17.0-202505280435.p0.gf9c412e.assembly.stream.el9 | RHSA-2025:8280 |
| Red Hat OpenShift Container Platform 4.18 | openshift4/ose-console-rhel9:v4.18.0-202505150334.p0.g75bc164.assembly.stream.el9 | RHSA-2025:7863 |
| Red Hat OpenShift Container Platform 4.14 | openshift4/ose-console:openshift-enterprise-console-container-v4.14.0-202510211320.p2.g0682746.assembly.stream.el8 | RHSA-2025:19058 |
| Red Hat OpenShift Container Platform 4.15 | openshift4/ose-console:openshift-enterprise-console-container-v4.15.0-202508180724.p2.g69615d5.assembly.stream.el8 | RHSA-2025:14397 |
Frequently Asked Questions
Is CVE-2024-6538 in your dependencies?
O3 Security finds CVE-2024-6538 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.