Keycloak AuthenticationApplication · Jenkins
CVE-2023-24457
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 Keycloak Authentication Plugin 2.3.0 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 · moderate confidenceCSRF vulnerability in the Jenkins Keycloak Authentication Plugin allows attackers to craft malicious links that trick authenticated users into logging into the attacker's Keycloak account, potentially exposing session data or enabling unauthorized actions under the attacker's identity.
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
Keycloak AuthenticationApplication
<= 2.3.0CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Keycloak Authentication Plugin is installedIn Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab, or inspect the Jenkins plugin directory for keycloak-authentication-plugin in $JENKINS_HOME/plugins/Affected if The Keycloak Authentication Plugin is present in Jenkins
-
Determine installed plugin versionIn Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed tab and find Keycloak Authentication Plugin to view the version, or check the manifest file at $JENKINS_HOME/plugins/keycloak-authentication-plugin/META-INF/MANIFEST.MFAffected if The version is 2.3.0 or lower
-
Confirm Keycloak authentication is enabledGo to Manage Jenkins > Configure Global Security > Security Realm and verify that 'Keycloak Authentication' is selected as the security realm, or inspect the Jenkins configuration XML file for the securityRealm setting containing KeycloakAffected if Keycloak is configured as the active authentication method in Jenkins
A user is affected if they have the Keycloak Authentication Plugin installed at version 2.3.0 or lower AND have Keycloak configured as their active Jenkins authentication realm.
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.
From vendor dataUpdate Keycloak Authentication Plugin to a version newer than 2.3.0 once patched; verify authentication flows work correctly after update.
Fix this in Keycloak Authentication
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-24457 — 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-24457 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