# CVE-2017-2607: Improper Neutralization of Input During Web Page Generation in Jenkins

> Attackers can inject malicious scripts into build logs via console notes, leading to XSS attacks against Jenkins users viewing those logs.

- **Severity:** Medium 4.2 (`CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/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:** Not needed
- **Fix available:** Yes
- **Published:** 21 May 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-42m6-7xff-9v9m

## What is CVE-2017-2607?

CVE-2017-2607 is a medium-severity cross-site scripting vulnerability in Jenkins Jenkins, published on 21 May 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

jenkins before versions 2.44, 2.32.2 is vulnerable to a persisted cross-site scripting vulnerability in console notes (SECURITY-382). Jenkins allows plugins to annotate build logs, adding new content or changing the presentation of existing content while the build is running. Malicious Jenkins users, or users with SCM access, could configure jobs or modify build scripts such that they print serialized console notes that perform cross-site scripting attacks on Jenkins users viewing the build logs.

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

## Which versions are affected by CVE-2017-2607?

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.32.2 |
| `org.jenkins-ci.main:jenkins-core` | Maven | All versions | 2.32.2 |
| `org.jenkins-ci.main:jenkins-core` | Maven | From 2.34 | 2.44 |
| `org.jenkins-ci.main:jenkins-core` | Maven | From 2.34 | 2.44 |

Products: Jenkins Jenkins.

## How do I fix CVE-2017-2607?

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

## Is CVE-2017-2607 being exploited?

There is no known exploitation of CVE-2017-2607 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-2017-2607 and fix it if it is affected.

What it is: CVE-2017-2607 is a medium-severity cross-site scripting vulnerability in Jenkins Jenkins, published on 21 May 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-2607 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.32.2
- org.jenkins-ci.main:jenkins-core (Maven): affected all versions; fixed in 2.32.2
- org.jenkins-ci.main:jenkins-core (Maven): affected from 2.34; fixed in 2.44
- org.jenkins-ci.main:jenkins-core (Maven): affected from 2.34; fixed in 2.44

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-2017-2607/ (Markdown: https://insights.sbomify.com/CVE-2017-2607/index.md)
```

## Sources

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

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