# CVE-2022-34171: Cross-site Scripting vulnerability in Jenkins

> Cross-site scripting vulnerability in Jenkins allows attackers to inject malicious scripts via unescaped SVG icon attributes, potentially leading to session hijacking or code execution.

- **Severity:** Medium 5.4 (`CVSS:3.1/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:** 22 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** BIT-jenkins-2022-34171, GHSA-7f84-p6r5-jr6q

## What is CVE-2022-34171?

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

### Official description

In Jenkins 2.321 through 2.355 (both inclusive) and LTS 2.332.1 through LTS 2.332.3 (both inclusive) the HTML output generated for new symbol-based SVG icons includes the 'title' attribute of 'l:ionicon' (until Jenkins 2.334) and 'alt' attribute of 'l:icon' (since Jenkins 2.335) without further escaping, resulting in a cross-site scripting (XSS) vulnerability.

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

## Which versions are affected by CVE-2022-34171?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.main:jenkins-core` | Maven | All versions | 2.332.4 |
| `org.jenkins-ci.main:jenkins-core` | Maven | All versions | 2.332.4 |
| `org.jenkins-ci.main:jenkins-core` | Maven | From 2.346 | 2.346.1 |
| `org.jenkins-ci.main:jenkins-core` | Maven | From 2.346 | 2.346.1 |
| `org.jenkins-ci.main:jenkins-core` | Maven | From 2.350 | 2.356 |
| `org.jenkins-ci.main:jenkins-core` | Maven | From 2.350 | 2.356 |
| `jenkins` | Bitnami | From 2.321.0 | 2.355.1 |

Products: Jenkins Jenkins.

## How do I fix CVE-2022-34171?

Upgrade org.jenkins-ci.main:jenkins-core to a fixed version for your release line: 2.332.4, 2.346.1 or 2.356.

## Is CVE-2022-34171 being exploited?

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

What it is: CVE-2022-34171 is a medium-severity cross-site scripting vulnerability in Jenkins Jenkins, published on 22 Jun 2022. 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-2022-34171 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.332.4
- org.jenkins-ci.main:jenkins-core (Maven): affected all versions; fixed in 2.332.4
- org.jenkins-ci.main:jenkins-core (Maven): affected from 2.346; fixed in 2.346.1
- org.jenkins-ci.main:jenkins-core (Maven): affected from 2.346; fixed in 2.346.1
- org.jenkins-ci.main:jenkins-core (Maven): affected from 2.350; fixed in 2.356
- org.jenkins-ci.main:jenkins-core (Maven): affected from 2.350; fixed in 2.356
- jenkins (Bitnami): affected from 2.321.0; fixed in 2.355.1

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

## Sources

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

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