# CVE-2022-27195: Sensitive parameter values captured in build metadata files by Jenkins Parameterized Trigger Plugin

> Attackers with file system access can read unencrypted passwords from build logs in the Jenkins Parameterized Trigger Plugin.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Mar 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-5mpf-hw8f-86w9

## What is CVE-2022-27195?

CVE-2022-27195 is a medium-severity vulnerability in Jenkins Parameterized Trigger Plugin, published on 15 Mar 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Jenkins Parameterized Trigger Plugin 2.43 and earlier captures environment variables passed to builds triggered using Jenkins Parameterized Trigger Plugin, including password parameter values, in their `build.xml` files. These values are stored unencrypted and can be viewed by users with access to the Jenkins controller file system.

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:parameterized-trigger` | Maven | All versions | 2.43.1 |
| `org.jenkins-ci.plugins:parameterized-trigger` | Maven | All versions | 2.43.1 |

Products: Jenkins Parameterized Trigger.

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

Upgrade org.jenkins-ci.plugins:parameterized-trigger to 2.43.1 or later.

## Is CVE-2022-27195 being exploited?

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

## Other vulnerabilities in Jenkins Parameterized Trigger Plugin

- [CVE-2017-1000084](https://insights.sbomify.com/CVE-2017-1000084/): Parameterized Trigger Plugin fails to check Item/Build permission (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-27195 is a medium-severity vulnerability in Jenkins Parameterized Trigger Plugin, published on 15 Mar 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-27195 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:parameterized-trigger (Maven): affected all versions; fixed in 2.43.1
- org.jenkins-ci.plugins:parameterized-trigger (Maven): affected all versions; fixed in 2.43.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-27195/ (Markdown: https://insights.sbomify.com/CVE-2022-27195/index.md)
```

## Sources

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

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