OpenidApplication · Jenkins
CVE-2023-24446
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 · uneditedA cross-site request forgery (CSRF) vulnerability in Jenkins OpenID Plugin 2.4 and earlier allows attackers to trick users into logging in to the attacker's account.
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 confidenceA CSRF vulnerability in Jenkins OpenID Plugin versions 2.4 and earlier allows attackers to manipulate the OpenID authentication flow to trick users into logging into the attacker's account, potentially enabling session hijacking or unauthorized access to Jenkins resources.
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
OpenidApplication
<= 2.4CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify OpenID Plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or run: jenkins-cli.jar who-is-who plugin or check $JENKINS_HOME/plugins/ for openid directoryAffected if The OpenID Plugin is not listed in installed plugins, then the vulnerability does not apply
-
Determine installed OpenID Plugin versionIn Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed tab and locate OpenID Plugin to view version number. Alternatively, check the version file in $JENKINS_HOME/plugins/openid/WEB-INF/MANIFEST.MFAffected if The installed version is 2.4 or earlier
-
Confirm OpenID authentication is enabledNavigate to Jenkins > Manage Jenkins > Configure Global Security and verify that 'OpenID' is selected as the Security Realm, or check the jenkins.model.JenkinsLocationConfiguration.xml and security realm settings in configuration filesAffected if OpenID is configured as the active authentication method; if a different security realm (such as Jenkins' own user database) is in use, exploitation is not possible
-
Review OpenID provider configurationNavigate to Jenkins > Manage Jenkins > Configure Global Security > OpenID settings and examine the configured OpenID provider endpoint and any trusted URLsAffected if The OpenID provider points to an untrusted or attacker-controlled server
User is affected if OpenID Plugin version 2.4 or earlier is installed AND OpenID authentication is enabled as the security realm in Jenkins.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade Jenkins OpenID Plugin to version 2.5 or later which contains the fix for this CSRF vulnerability.
Version greater than 2.4 (e.g., 2.5 or latest available)
- Navigate to Jenkins Manage Plugins page
- Locate the OpenID Plugin in the installed plugins list
- Check for available updates - upgrade to a version greater than 2.4
- Restart Jenkins if required after the upgrade
- Verify the plugin updated successfully
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Openid
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2023-24446 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-24446 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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