# CVE-2019-10395: Jenkins Build Environment Plugin vulnerable to Cross-site Scripting

> Cross-site scripting in Jenkins Build Environment Plugin allows attackers to execute scripts via unescaped variables in job views.

- **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:** 12 Sep 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-88qj-3q6h-8m5q

## What is CVE-2019-10395?

CVE-2019-10395 is a medium-severity cross-site scripting vulnerability in Jenkins Build Environment Plugin, published on 12 Sep 2019. 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 Build Environment Plugin 1.6 and earlier did not escape variables shown on its views, resulting in a cross-site scripting vulnerability in Jenkins 2.145, 2.138.1, or older, exploitable by users able to change various job/build properties.

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

## Which versions are affected by CVE-2019-10395?

2 open source packages ship an affected version, including org.jenkins-ci.plugins:build-environment. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:build-environment` | Maven | All versions | 1.7 |
| `org.jenkins-ci.plugins:build-environment` | Maven | All versions | 1.7 |

Products: Jenkins Build Environment.

## How do I fix CVE-2019-10395?

Upgrade org.jenkins-ci.plugins:build-environment to 1.7 or later.

## Is CVE-2019-10395 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-10395 and fix it if it is affected.

What it is: CVE-2019-10395 is a medium-severity cross-site scripting vulnerability in Jenkins Build Environment Plugin, published on 12 Sep 2019. 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-2019-10395 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:build-environment (Maven): affected all versions; fixed in 1.7
- org.jenkins-ci.plugins:build-environment (Maven): affected all versions; fixed in 1.7

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

## Sources

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

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