JenkinsApplication
CVE-2018-1000170
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 scripting vulnerability exists in Jenkins 2.115 and older, LTS 2.107.1 and older, in confirmationList.jelly and stopButton.jelly that allows attackers with Job/Configure and/or Job/Create permission to create an item name containing JavaScript that would be executed in another user's browser when that other user performs some UI actions.
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 stored cross-site scripting vulnerability in Jenkins confirmationList.jelly and stopButton.jelly allows attackers with Job/Configure or Job/Create permissions to embed malicious JavaScript in item names, which executes in other users' browsers when they interact with affected UI elements.
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
JenkinsApplication
<= 2.105<= 2.107.1CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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.
-
Identify installed Jenkins versionNavigate to Manage Jenkins > About Jenkins or check the version shown on the login page and bottom-right of the dashboard. Compare this version number against the affected ranges: any version <= 2.105 or any version <= 2.107.1Affected if The installed version falls within <= 2.105 or <= 2.107.1
-
Verify Job/Configure and Job/Create permissions existNavigate to Manage Jenkins > Manage Users and check if any users or groups are granted the Job/Configure or Job/Create permissions. These permissions are typically assigned through the matrix authorization strategy under Manage Jenkins > Configure Global SecurityAffected if Any untrusted user or group has Job/Configure or Job/Create permissions enabled
-
Inspect item names for suspicious contentList all jobs/items in Jenkins (view the main dashboard) and visually inspect item names for unusual characters, HTML tags, or JavaScript-like patterns such as <script, javascript:, onerror=, or other encoded payloadsAffected if Any job or item name contains JavaScript code, HTML tags, or event handler attributes that could execute in a browser
-
Check for presence of vulnerable UI filesVerify the Jenkins web application serves the jelly files confirmationList.jelly and stopButton.jelly. These are typically found in the Jenkins WAR file under /webapp/scripts/ or accessed indirectly through the UI when stopping builds or confirming actionsAffected if The Jenkins instance serves these UI components (which it does in affected versions) and users interact with build stopping or confirmation dialogs
You are affected if your Jenkins version is 2.105 or earlier, or between 2.106 and 2.107.1, AND untrusted users have Job/Configure or Job/Create permissions, OR if you observe suspicious item names containing script tags or JavaScript code.
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 to version 2.115.1 or LTS 2.107.2 or later to patch the XSS vulnerability; alternatively, restrict Job/Configure and Job/Create permissions to trusted users only.
Fix this in Jenkins
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1000170 — 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-1000170 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