dbcve.org
Openid Connect AuthenticationApplication · Jenkins

CVE-2023-24424

HIGH · 8.8 CVSS v3.1 Published 2023-01-26
Fix available
A fix is available. Upgrade to 2.5 or later.
See remediation →
95/100
Remediation priority · Urgent
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.4 and earlier does not invalidate the previous session on login.

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 versions 2.4 and earlier does not invalidate the previous session upon user login, creating a session fixation vulnerability. An attacker with access to a user's session ID could potentially continue using that session after the legitimate user authenticates.

MitigationUpgrade the OpenID Connect Authentication Plugin to version 2.5 or later, which includes proper session invalidation on login.

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.5

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 Authentication' or 'Openid Connect Authentication', or use the Jenkins CLI: java -jar jenkins-cli.jar list-plugins | findstr -i openid
    Affected if The plugin appears in the installed plugins list
  2. Check the installed version of the OpenID Connect Authentication Plugin
    In Manage Jenkins > Manage Plugins > Installed tab, find the OpenID Connect Authentication plugin and note the version number displayed in the 'Version' column
    Affected if The version shown is 2.4 or earlier (versions below 2.5)
  3. Confirm OIDC authentication is configured
    Navigate to Manage Jenkins > Configure Global Security and verify that 'OpenID Connect' is selected as the Security Realm / Authentication method, or check the configuration file (usually $JENKINS_HOME/org.jenkinsci.plugins.openidconnect.OpenIDChangeRealm.xml or similar XML config files in $JENKINS_HOME) for OIDC realm configuration
    Affected if OIDC/OpenID Connect is enabled as the authentication method

A user is affected if the OpenID Connect Authentication Plugin is installed with version 2.4 or earlier and OIDC/OpenID Connect authentication is enabled as the security realm in Jenkins.

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 2.5 or later
Fixed in 2.5
Interim mitigation

Upgrade the OpenID Connect Authentication Plugin to version 2.5 or later, which includes proper session invalidation on login.

Recommended fix High confidence

OpenId Connect Authentication Plugin version 2.5

  1. Log in to Jenkins as an administrator
  2. Navigate to 'Manage Jenkins' > 'Manage Plugins'
  3. Go to the 'Installed' tab
  4. Locate the 'OpenId Connect Authentication' plugin in the list
  5. If the current version is below 2.5, select the plugin and click 'Update now' or 'Download now' after checking for updates
  6. Wait for the plugin to download and install
  7. Restart Jenkins (either manually or allow Jenkins to restart if the UI prompts)
  8. Verify the plugin version is now 2.5 or higher under 'Manage Jenkins' > 'Manage Plugins' > 'Installed'

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
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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