CVE-2023-37947 — openshift-login
MEDIUMCVE-2023-37947 is a medium-severity (CVSS 4.3) Open Redirect vulnerability in org.openshift.jenkins:openshift-login. A fix is available for org.openshift.jenkins:openshift-login — see the affected versions and patch details below.
Jenkins OpenShift Login Plugin vulnerable to Open Redirect
Exploitation Status
No confirmed exploitation observed yet
- 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-2023-37947.
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-2023-37947 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 379,145 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
org.openshift.jenkins:openshift-loginReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Jenkins OpenShift Login Plugin 1.1.0.227.v27e08dfb_1a_20 and earlier improperly determines that a redirect URL after login is legitimately pointing to Jenkins.
This allows attackers to perform phishing attacks by having users go to a Jenkins URL that will forward them to a different site after successful authentication.
OpenShift Login Plugin 1.1.0.230.v5d7030b_f5432 only redirects to relative (Jenkins) URLs.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.openshift.jenkins:openshift-login | all versions | 1.1.0.230.v5d7030borg.openshift.jenkins:openshift-login:1.1.0.230.v5d7030b |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.openshift.jenkins:openshift-login, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.openshift.jenkins:openshift-login to 1.1.0.230.v5d7030b or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-37947 is resolved across your whole dependency graph.
Workarounds
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-2023-37947 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2023-37947. 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 |
|---|---|---|
| OCP-Tools-4.12-RHEL-8 | jenkins-2-plugins-0:4.12.1706515741-1.el8 | RHSA-2024:0778 |
| OCP-Tools-4.14-RHEL-8 | jenkins-2-plugins-0:4.14.1706516441-1.el8 | RHSA-2024:0777 |
Frequently Asked Questions
Is CVE-2023-37947 in your dependencies?
O3 Security finds CVE-2023-37947 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.