# CVE-2022-34787: Jenkins Project Inheritance Plugin vulnerable to cross site scripting

> Attackers can inject malicious scripts into Jenkins build block reason tooltips, potentially compromising user sessions.

- **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:** No
- **Published:** 30 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-3hx4-285w-v6mm

## What is CVE-2022-34787?

CVE-2022-34787 is a medium-severity cross-site scripting vulnerability in Jenkins Project Inheritance Plugin, published on 30 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

Jenkins Project Inheritance Plugin 21.04.03 and earlier does not escape the reason a build is blocked in tooltips, resulting in a cross-site scripting (XSS) vulnerability exploitable by attackers able to control the reason a queue item is blocked.

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

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

2 open source packages ship an affected version, including hudson.plugins:project-inheritance. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `hudson.plugins:project-inheritance` | Maven | All versions to 21.04.03 | None |
| `hudson.plugins:project-inheritance` | Maven | All versions to 21.04.03 | None |

Products: Jenkins Project Inheritance.

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

No fix has been published for CVE-2022-34787 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-34787 being exploited?

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

## Other vulnerabilities in Jenkins Project Inheritance Plugin

- [CVE-2020-2198](https://insights.sbomify.com/CVE-2020-2198/): Missing permission check in Jenkins Project Inheritance Plugin (medium 6.5)
- [CVE-2019-10407](https://insights.sbomify.com/CVE-2019-10407/): Project Inheritance Plugin showed secret environment variables defined in Mask Passwords Plugin (medium 6.5)
- [CVE-2020-2197](https://insights.sbomify.com/CVE-2020-2197/): Missing permission check in Jenkins Project Inheritance Plugin (medium 4.3)
- [CVE-2019-10408](https://insights.sbomify.com/CVE-2019-10408/): Jenkins Project Inheritance Plugin vulnerable to Cross-Site Request Forgery (medium 4.3)
- [CVE-2019-10409](https://insights.sbomify.com/CVE-2019-10409/): Missing permission check in Jenkins Project Inheritance Plugin (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-34787 and fix it if it is affected.

What it is: CVE-2022-34787 is a medium-severity cross-site scripting vulnerability in Jenkins Project Inheritance Plugin, published on 30 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-34787 in the wild and no public exploit code.

Affected packages and fixed versions:
- hudson.plugins:project-inheritance (Maven): affected all versions up to 21.04.03; no fix listed
- hudson.plugins:project-inheritance (Maven): affected all versions up to 21.04.03; no fix listed

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

## Sources

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

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