Saml Single Sign OnApplication · Jenkins
CVE-2023-32992
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 · uneditedMissing permission checks in Jenkins SAML Single Sign On(SSO) Plugin 2.0.2 and earlier allow attackers with Overall/Read permission to send an HTTP request to an attacker-specified URL and parse the response as XML, or parse a local file on the Jenkins controller as XML.
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 confidenceThe Jenkins SAML SSO Plugin versions 2.0.2 and earlier lack permission checks, allowing any user with Overall/Read permission to trigger the Jenkins controller to make HTTP requests to attacker-specified URLs and parse the responses as XML, or read and parse local files on the controller as XML. This creates SSRF and potential XXE attack vectors.
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
Saml Single Sign OnApplication
<= 2.0.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify the SAML SSO plugin is installedGo to Manage Jenkins > Manage Plugins > Installed tab, or list contents of $JENKINS_HOME/plugins/ directory, and look for 'Saml Single Sign On' or 'SAML SSO' pluginAffected if The plugin is present in the installed plugins list
-
Determine the installed plugin versionIn the Installed Plugins tab, locate the Saml Single Sign On plugin and note the Version column; alternatively, check the plugin's manifest file (MANIFEST.MF) inside its plugin folderAffected if The displayed version is 2.0.2 or any version lower than 2.0.2
-
Confirm the vulnerability is exploitable by checking user permissionsGo to Manage Jenkins > Manage Users, or review the authorization matrix in Manage Jenkins > Global Security, and identify users or groups granted the Overall/Read permissionAffected if Any user account exists with Overall/Read permission enabled, which is the default in most Jenkins installations
-
Check if the plugin configuration exposes SAML-related endpointsReview the plugin configuration at Manage Jenkins > Configure Global Security > SAML SSO settings, or access the API endpoint /securityRealm/finishLogin (if accessible) to confirm the plugin routing is activeAffected if The SAML SSO plugin is configured and actively routing authentication requests
If the Saml Single Sign On plugin is installed at version 2.0.2 or earlier, and any user has Overall/Read permission (the default setting), the environment is affected by this vulnerability.
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 the Jenkins SAML SSO Plugin to a version newer than 2.0.2. As a temporary mitigation, restrict network access from the Jenkins controller and review plugin usage policies until the update can be applied.
Fix this in Saml Single Sign On
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-32992 — 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-32992 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