dbcve.org
Azure AdApplication · Jenkins

CVE-2023-24426

HIGH · 8.8 CVSS v3.1 Published 2023-01-26
Fix available
A fix is available. Upgrade to after 303.va_91ef20ee49f 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 Azure AD Plugin 303.va_91ef20ee49f 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 · moderate confidence

The Jenkins Azure AD Plugin fails to invalidate the previous session upon user login, allowing session fixation where an attacker with access to a prior session can continue using it even after legitimate re-authentication. This breaks the standard security practice of session renewal on authentication.

MitigationUpdate the Jenkins Azure AD Plugin to the latest version that properly invalidates previous sessions on login, then verify Azure AD authentication continues functioning correctly.

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
Azure AdApplication
Affected:<= 303.va_91ef20ee49f

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 Jenkins Azure AD Plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Azure AD' or list installed plugins via Jenkins CLI: jenkins-cli.jar list-plugins
    Affected if Azure AD Plugin appears in the installed plugins list
  2. Determine installed Azure AD Plugin version
    In the Installed Plugins tab, locate the Azure AD Plugin and note the Version column; or use: jenkins-cli.jar list-plugins | grep -i azure
    Affected if Version number is visible and is 303.va_91ef20ee49f or lower
  3. Confirm Azure AD authentication is configured
    Navigate to Manage Jenkins > Configure Global Security > Security Realm and verify 'Azure AD' is selected as the security realm
    Affected if Azure AD authentication is enabled as the security realm in Jenkins global security settings
  4. Compare version against affected range
    If the installed version is <= 303.va_91ef20ee49f, the plugin is within the vulnerable version range
    Affected if Installed version is 303.va_91ef20ee49f or any lower version number

User is affected if the Azure AD Plugin is installed with version 303.va_91ef20ee49f or lower and Azure AD authentication is enabled as the Jenkins security realm.

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 303.va_91ef20ee49f
Interim mitigation

Update the Jenkins Azure AD Plugin to the latest version that properly invalidates previous sessions on login, then verify Azure AD authentication continues functioning correctly.

Recommended fix High confidence

Latest available version of Azure AD plugin (check Jenkins Security Advisory for CVE-2023-24426 for exact version)

  1. Check the Jenkins Security Advisory (https://www.jenkins.io/security/advisory/) for CVE-2023-24426 to confirm the exact fixed version number
  2. Navigate to Manage Jenkins > Manage Plugins > Installed tab
  3. Locate the 'Azure AD' plugin in the list
  4. If a newer version than 303.va_91ef20ee49f is available, select it and click 'Update'
  5. Restart Jenkins after the update completes
  6. Verify that users are required to re-authenticate after the update (this confirms session invalidation is now working)

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

Fix this in Azure Ad Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,010
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,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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