dbcve.org
Openid Connect AuthenticationApplication · Jenkins

CVE-2025-24399

HIGH · 8.8 CVSS v3.1 Published 2025-01-22
Fix available
A fix is available. Upgrade to 4.438.440.v3f5f201de5dc / 4.453.v4d7765c854f4 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 4.452.v2849b_d3945fa_ and earlier, except 4.438.440.v3f5f201de5dc, treats usernames as case-insensitive, allowing attackers on Jenkins instances configured with a case-sensitive OpenID Connect provider to log in as any user by providing a username that differs only in letter case, potentially gaining administrator access to Jenkins.

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 incorrectly treats usernames as case-insensitive while the underlying OIDC provider may be case-sensitive. This mismatch allows attackers to impersonate any user (including administrators) by submitting a username that differs only in letter case (e.g., 'admin' vs 'Admin'), bypassing authentication controls.

MitigationUpdate the Jenkins OpenID Connect Authentication Plugin to the patched version (4.438.440.v3f5f201de5dc or later). If immediate patching is not possible, review user accounts in the OIDC provider and restrict privileged accounts to prevent case-squatting exploitation.

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:< 4.438.440.v3f5f201de5dc>= 4.444.vd4c54f157201, < 4.453.v4d7765c854f4

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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. Confirm OpenID Connect plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed and search for 'OpenID Connect' or 'Openid Connect Authentication' in the list of installed plugins
    Affected if The plugin appears in the installed plugins list and OIDC authentication is in use for Jenkins login
  2. Identify the installed plugin version
    In the Manage Plugins > Installed page, locate the OpenID Connect Authentication plugin and note the version number displayed in the Version column
    Affected if The installed version is less than 4.438.440.v3f5f201de5dc, OR the version is 4.444.vd4c54f157201 or higher but less than 4.453.v4d7765c854f4
  3. Verify OIDC authentication is enabled
    Navigate to Manage Jenkins > Security > Security Realm and confirm the security realm is set to 'OpenID Connect Authentication' or a similar OIDC provider option
    Affected if The Security Realm is configured to use OpenID Connect Authentication, enabling the vulnerable case-handling logic
  4. Check user sync configuration for case sensitivity
    Review the OpenID Connect plugin configuration at Manage Jenkins > Security > OpenID Connect and look for settings related to user name mapping, user name attribute, or user groups. Inspect whether the plugin performs any case normalization on usernames during authentication
    Affected if The plugin configuration does not enforce strict case matching between Jenkins usernames and OIDC provider user identifiers, and privileged accounts exist in Jenkins that could be impersonated via case variation

A user is affected if the OpenID Connect Authentication plugin is installed with a version in the vulnerable ranges AND OIDC authentication is actively configured as the security realm, particularly if privileged Jenkins accounts (such as administrators) exist that could be impersonated through case variation.

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 4.438.440.v3f5f201de5dc / 4.453.v4d7765c854f4 or later
Fixed in 4.438.440.v3f5f201de5dc4.453.v4d7765c854f4
Interim mitigation

Update the Jenkins OpenID Connect Authentication Plugin to the patched version (4.438.440.v3f5f201de5dc or later). If immediate patching is not possible, review user accounts in the OIDC provider and restrict privileged accounts to prevent case-squatting exploitation.

Recommended fix High confidence

4.453.v4d7765c854f4

  1. 1. Back up your Jenkins configuration and plugins directory
  2. 2. Navigate to Manage Jenkins > Manage Plugins
  3. 3. Go to the 'Installed' tab
  4. 4. Locate the 'OpenId Connect Authentication' plugin in the list
  5. 5. If auto-updates are enabled, the plugin may update automatically; otherwise, check for updates via the 'Updates' tab
  6. 6. Select the plugin and click 'Update' or 'Download now and install after restart'
  7. 7. Wait for the update to complete and Jenkins to restart
  8. 8. Verify the installed version is 4.453.v4d7765c854f4 or later via Manage Plugins > Installed tab

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
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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