# CVE-2018-1000170: Cross-site Scripting in Jenkins Core

> Attackers with job configuration permissions can inject JavaScript into item names, executing code in other users' browsers during UI interactions.

- **Severity:** Medium 5.4 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 13 Apr 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-9jcv-v4jp-w3cq

## What is CVE-2018-1000170?

CVE-2018-1000170 is a medium-severity cross-site scripting vulnerability in Jenkins Jenkins, published on 13 Apr 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A 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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2018-1000170?

4 open source packages ship an affected version, including org.jenkins-ci.main:jenkins-core. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.main:jenkins-core` | Maven | All versions | 2.107.2 |
| `org.jenkins-ci.main:jenkins-core` | Maven | All versions | 2.107.2 |
| `org.jenkins-ci.main:jenkins-core` | Maven | From 2.108 | 2.116 |
| `org.jenkins-ci.main:jenkins-core` | Maven | From 2.108 | 2.116 |

Products: Jenkins Jenkins.

## How do I fix CVE-2018-1000170?

Upgrade org.jenkins-ci.main:jenkins-core to a fixed version for your release line: 2.107.2 or 2.116.

## Is CVE-2018-1000170 being exploited?

There is no known exploitation of CVE-2018-1000170 in the wild and no public exploit code.

## Other vulnerabilities in Jenkins Jenkins

- [CVE-2024-23897](https://insights.sbomify.com/CVE-2024-23897/): Jenkins Command Line Interface (CLI) Path Traversal (critical 9.8, exploited in the wild)
- [CVE-2018-1000861](https://insights.sbomify.com/CVE-2018-1000861/): Jenkins Stapler Web Framework Deserialization of Untrusted Data (critical 9.8, exploited in the wild)
- [CVE-2017-1000353](https://insights.sbomify.com/CVE-2017-1000353/): Jenkins Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2015-5317](https://insights.sbomify.com/CVE-2015-5317/): Jenkins User Interface (UI) Information Disclosure (high 7.5, exploited in the wild)
- [CVE-2021-21690](https://insights.sbomify.com/CVE-2021-21690/): Multiple vulnerabilities allow bypassing path filtering of agent-to-controller access control in Jenkins (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-1000170 and fix it if it is affected.

What it is: CVE-2018-1000170 is a medium-severity cross-site scripting vulnerability in Jenkins Jenkins, published on 13 Apr 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-1000170 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.main:jenkins-core (Maven): affected all versions; fixed in 2.107.2
- org.jenkins-ci.main:jenkins-core (Maven): affected all versions; fixed in 2.107.2
- org.jenkins-ci.main:jenkins-core (Maven): affected from 2.108; fixed in 2.116
- org.jenkins-ci.main:jenkins-core (Maven): affected from 2.108; fixed in 2.116

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-1000170/ (Markdown: https://insights.sbomify.com/CVE-2018-1000170/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-1000170
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-1000170
- OSV: https://osv.dev/vulnerability/CVE-2018-1000170

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-1000170/
Summaries are generated and may contain mistakes; the official description above is the record.