Security readout for executives and security teams
Plain-English summary
This Jenkins issue lets a user who can create or configure jobs choose a malicious item name that can run JavaScript in another user’s browser during certain Jenkins UI actions. It is not described as unauthenticated or remotely exploitable without permissions, but it can still affect administrator sessions and trust boundaries inside Jenkins.
Executive priority
Treat as a moderate-priority Jenkins hardening and patching issue. It is permission-gated, but Jenkins often holds sensitive build, deployment, and credential context, so older shared controllers should be addressed promptly.
Technical view
CVE-2018-1000170 is a cross-site scripting flaw in Jenkins confirmationList.jelly and stopButton.jelly. Affected versions are Jenkins 2.115 and older and Jenkins LTS 2.107.1 and older. The source states exploitation requires Job/Configure and/or Job/Create permission and depends on another user triggering affected UI behavior.
Likely exposure
Exposure is most likely in older Jenkins controllers where non-administrators, automation accounts, or broad groups have Job/Create or Job/Configure permissions. Public internet exposure increases business risk, but the cited sources do not state unauthenticated exploitation.
Exploitation context
The source bundle does not report active exploitation, and CISA KEV status is false. The described attacker already needs Jenkins job creation or configuration privileges, then relies on another user using affected UI paths where the crafted item name is rendered.
Researcher notes
Evidence is limited to the CVE description and Jenkins advisory reference. No CVSS vector, CWE, proof of exploitation, or detailed patch text is present in the supplied bundle. Do not assume affected plugins or products beyond Jenkins core versions named here.
Mitigation direction
- Review Jenkins advisory SECURITY-759 for the vendor’s fixed-version guidance.
- Upgrade Jenkins if running 2.115 or older, or LTS 2.107.1 or older.
- Restrict Job/Create and Job/Configure permissions to trusted users only.
- Review Jenkins item names created by users with those permissions.
- Prioritize remediation on internet-facing or shared Jenkins controllers.
Validation and detection
- Inventory Jenkins controller versions and compare against the affected ranges.
- Identify users and groups with Job/Create or Job/Configure permissions.
- Check whether older controllers are exposed to untrusted networks.
- Review recent job or item creations by non-administrative users.
- Confirm remediation against the Jenkins SECURITY-759 advisory.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2018-1000170 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://jenkins.io/security/advisory/2018-04-11/#SECURITY-759CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.