SamlApplication · Jenkins
CVE-2018-1000602
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 session fixation vulnerability exists in Jenkins SAML Plugin 1.0.6 and earlier in SamlSecurityRealm.java that allows unauthorized attackers to impersonate another users if they can control the pre-authentication session.
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 confidenceSession fixation vulnerability in Jenkins SAML Plugin versions 1.0.6 and earlier. The SamlSecurityRealm.java implementation fails to regenerate session identifiers after SAML authentication completes, allowing an attacker who controls the pre-authentication session to hijack the authenticated session and impersonate the victim.
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
SamlApplication
<= 1.0.6CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/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.
-
Confirm Jenkins is runningAccess the Jenkins web UI or check for the Java process (for example, running 'ps aux | grep jenkins' or checking if port 8080 is listening)Affected if Jenkins is not running, this CVE does not apply
-
Verify SAML Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed, or list files in the $JENKINS_HOME/plugins/ directory and look for 'saml' or 'SAML' in the folder namesAffected if The SAML Plugin is not installed, this vulnerability does not apply
-
Check SAML Plugin versionIn the Jenkins web UI, go to Manage Jenkins > Manage Plugins > Installed and locate the SAML Plugin entry to view its version number. Compare this to the affected version range of 1.0.6 and earlierAffected if The installed version is 1.0.6 or earlier (for example, 1.0.5, 1.0.4, etc.)
-
Confirm SAML authentication is enabledNavigate to Manage Jenkins > Configure Global Security and examine the Security Realm setting. Check if it is set to 'SAML 2.0' or 'SAML Plugin' indicating SAML is the active authentication methodAffected if SAML is not configured as the Security Realm, the session fixation flaw cannot be exploited against this instance
A user is affected if they are running Jenkins with the SAML Plugin at version 1.0.6 or earlier and have SAML configured as their Security Realm for authentication.
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 dataUpgrade Jenkins SAML Plugin to a version newer than 1.0.6 that implements proper session ID regeneration after successful SAML authentication.
Fix this in Saml
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1000602 — 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-2018-1000602 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