dbcve.org
Openid Connect AuthenticationApplication · Jenkins

CVE-2023-50771

MEDIUM · 6.1 CVSS v3.1 Published 2023-12-13
Fix available
A fix is available. Upgrade to after 2.6 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 OpenId Connect Authentication Plugin 2.6 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 OpenID Connect Authentication Plugin 2.6 and earlier contains an open redirect vulnerability where it improperly validates that redirect URLs after successful OIDC login point to legitimate Jenkins instances, allowing attackers to craft malicious authentication flows that redirect users to phishing sites.

MitigationUpgrade the OpenID Connect Authentication Plugin to a patched version that properly validates redirect URLs, or configure the identity provider to restrict allowed redirect URIs to known Jenkins endpoints.

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
Openid Connect AuthenticationApplication
Affected:<= 2.6

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. Verify OpenID Connect Authentication plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'OpenID Connect' or 'Openid Connect Authentication' in the plugin list. Check the 'Version' column.
    Affected if Plugin is installed and version is 2.6 or earlier (e.g., 2.6, 2.5, 2.4, etc.)
  2. Confirm OIDC authentication is actually enabled
    Go to Manage Jenkins > Global Security > Security Realm section. Verify that 'OpenID Connect' or 'OAuth' is selected as the Security Realm. The vulnerability only applies if OIDC login is actively configured.
    Affected if OIDC/OAuth-based authentication is selected as the security realm in Global Security settings
  3. Inspect the configured redirect URIs
    Navigate to Manage Jenkins > Configure Global Security > OpenID Connect / OAuth section. Review the 'Redirect URL' or 'Redirect URI' configuration. Check if the identity provider (IdP) settings restrict allowed redirect URIs.
    Affected if Redirect URIs are not explicitly restricted to known Jenkins endpoints or the configuration allows arbitrary external redirects after authentication
  4. Check identity provider redirect URI configuration
    If using an external IdP (such as Azure AD, Google, Okta, etc.), log into the IdP admin console and review the registered redirect URIs for the Jenkins application. Verify they point only to legitimate Jenkins base URLs.
    Affected if The IdP allows redirect URIs that could be manipulated to point to external/phishing domains

Your environment is affected if the OpenID Connect Authentication Plugin version 2.6 or earlier is installed AND OIDC authentication is enabled, regardless of how the redirect URIs are currently configured.

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 a release after 2.6
Interim mitigation

Upgrade the OpenID Connect Authentication Plugin to a patched version that properly validates redirect URLs, or configure the identity provider to restrict allowed redirect URIs to known Jenkins endpoints.

Recommended fix High confidence

OpenId Connect Authentication Plugin version 2.7 or later

  1. Navigate to Jenkins dashboard
  2. Go to Manage Jenkins > Manage Plugins
  3. Select the 'Installed' tab
  4. Locate the 'OpenId Connect Authentication' plugin in the list
  5. Check if the current version is 2.6 or earlier
  6. If vulnerable, click 'Update' to install the latest version
  7. Restart Jenkins if required to complete the update
  8. Verify the installed version is greater than 2.6
Caveat Review plugin configuration after upgrade as some settings may need adjustment

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

Fix this in Openid Connect Authentication Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-50771 — 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-50771 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