dbcve.org
Openshift LoginApplication · Jenkins

CVE-2023-37947

MEDIUM · 6.1 CVSS v3.1 Published 2023-07-12
Fix available
A fix is available. Upgrade to 1.1.0.230.v5d7030b_f5432 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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, allowing attackers to perform phishing attacks.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Jenkins OpenShift Login Plugin before version 1.1.0.227.v27e08dfb_1a_20 contains an open redirect vulnerability in its authentication flow. After a user successfully authenticates via OpenShift, the plugin fails to properly validate that the post-login redirect URL points to the legitimate Jenkins instance, allowing attackers to craft malicious links that redirect authenticated users to external phishing sites.

MitigationUpdate Jenkins OpenShift Login Plugin to the latest patched version. If unable to update immediately, users should verify redirect URLs before clicking login links from untrusted sources.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Openshift LoginApplication
Affected:< 1.1.0.230.v5d7030b_f5432

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed OpenShift Login Plugin version
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and locate the 'OpenShift Login' plugin in the list. The version column shows the currently installed version.
    Affected if The installed version is lower than 1.1.0.230.v5d7030b_f5432.
  2. Confirm OpenShift Login authentication is configured
    Navigate to Jenkins > Manage Jenkins > Configure Global Security > Authentication. Check if 'OpenShift Login' appears in the list of active Security Realm providers.
    Affected if The OpenShift Login plugin is enabled as an active authentication method.
  3. Verify OpenShift client plugin dependency
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and confirm the 'OpenShift Client Plugin' is also installed, as OpenShift Login depends on it.
    Affected if Both the OpenShift Login and OpenShift Client plugins are installed.
  4. Check for redirect URL validation in plugin configuration
    Review the plugin configuration at Jenkins > Manage Jenkins > Configure Global Security. Look for the OpenShift Login section and examine any redirect or URL settings configured for post-login behavior.
    Affected if A custom redirect URL is configured or if the plugin handles redirect parameters without strict validation.

A user is affected if the Jenkins OpenShift Login Plugin version is below 1.1.0.230.v5d7030b_f5432 AND the plugin is enabled as an active authentication method in the Jenkins security configuration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.1.0.230.v5d7030b_f5432 or later
Fixed in 1.1.0.230.v5d7030b_f5432
Interim mitigation

Update Jenkins OpenShift Login Plugin to the latest patched version. If unable to update immediately, users should verify redirect URLs before clicking login links from untrusted sources.

Recommended fix High confidence

1.1.0.230.v5d7030b_f5432

  1. 1. Log in to Jenkins as an administrator
  2. 2. Navigate to 'Manage Jenkins' > 'Manage Plugins'
  3. 3. Go to the 'Installed' tab
  4. 4. Locate the 'OpenShift Login' plugin in the list
  5. 5. If the currently installed version is below 1.1.0.230.v5d7030b_f5432, click 'Update' to upgrade to the fixed version
  6. 6. After the update completes, restart Jenkins if required
  7. 7. Verify the plugin shows version 1.1.0.230.v5d7030b_f5432 or later

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Openshift Login Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-37947 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-37947 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data