How severe is CVE-2023-37947?

CVE-2023-37947 has a CVSS score of 4.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2023-37947?

CVE-2023-37947 affects the following packages: org.openshift.jenkins:openshift-login (Maven). Ecosystems affected: Maven.

How do I fix CVE-2023-37947?

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.

How do I detect CVE-2023-37947 in my Maven dependencies?

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.

How do I mitigate CVE-2023-37947 if there is no patch (or I can't update yet)?

Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.

Is CVE-2023-37947 actively exploited in the wild?

No public exploit code has been indexed for CVE-2023-37947 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2023-37947?

CVE-2023-37947 has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 47th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2023-37947?

CVE-2023-37947 is classified as Open Redirect (CWE-601). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2023-37947 published, and has it been updated?

CVE-2023-37947 was published on July 12, 2023 and was last updated on February 16, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

CVE-2023-37947 — openshift-login

MEDIUM

CVE-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

Published

Jul 12, 2023

Updated

Feb 16, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs47th percentile — riskier than 47% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

☕org.openshift.jenkins:openshift-login

Real-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

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.openshift.jenkins:openshift-login`	all versions	1.1.0.230.v5d7030b`org.openshift.jenkins:openshift-login:1.1.0.230.v5d7030b`

Affected Products

1 product · 1 configurations

Application

openshift loginjenkins

< 1.1.0.230.v5d7030b_f5432

range

Detection & mitigation playbook

Open-source dependency

Detect
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
Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.

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.

Red HatModerate

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

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.

O3 Security · Impact-Aware SCA

Is CVE-2023-37947 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

4.3/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

None

Integrity

Low

Availability

None

Raw vector

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

CWE Classification

CWE-601Open Redirect

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Jul 12, 2023

Last updated

Feb 16, 2024

Identifiers

CVE-2023-37947

References

Advisorynvd.nist.gov · CVE 2023 37947 Webjenkins.io · 2023 07 12 Webopenwall.com

Related vulnerabilities

Also affects openshift-login

This CVE is medium severity; 1 of 1 other CVE affecting openshift-login is rated as high or higher (top: high).

CVE-2023-37946

Same weakness: CWE-601

This CVE is medium severity; 4 of 7 other CVEs with CWE-601 are rated as high or higher (top: moderate).

CVE-2026-77433CVE-2026-118658CVE-2026-116578CVE-2026-118656CVE-2026-114614CVE-2026-114060CVE-2026-111754Browse all CWE-601

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedFeb 16, 2024

CVE-2023-37947 — openshift-login

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2023-37947 in your dependencies?