# CVE-2020-2239: Secret stored in plain text by Jenkins Parameterized Remote Trigger Plugin

> Attackers with Jenkins controller file system access can read unencrypted secrets stored by the Parameterized Remote Trigger Plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/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:** 1 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-wphq-j78p-fhgp

## What is CVE-2020-2239?

CVE-2020-2239 is a medium-severity vulnerability in Jenkins Parameterized Remote Trigger Plugin, published on 1 Sep 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Jenkins Parameterized Remote Trigger Plugin 3.1.3 and earlier stores a secret unencrypted in its global configuration file on the Jenkins controller where it can be viewed by attackers with access to the Jenkins controller file system.

Weakness: CWE-311 (Missing Encryption of Sensitive Data)

## Which versions are affected by CVE-2020-2239?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:Parameterized-Remote-Trigger` | Maven | All versions | 3.1.4 |
| `org.jenkins-ci.plugins:Parameterized-Remote-Trigger` | Maven | All versions | 3.1.4 |

Products: Jenkins Parameterized Remote Trigger.

## How do I fix CVE-2020-2239?

Upgrade org.jenkins-ci.plugins:Parameterized-Remote-Trigger to 3.1.4 or later.

## Is CVE-2020-2239 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-2239 and fix it if it is affected.

What it is: CVE-2020-2239 is a medium-severity vulnerability in Jenkins Parameterized Remote Trigger Plugin, published on 1 Sep 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-2239 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:Parameterized-Remote-Trigger (Maven): affected all versions; fixed in 3.1.4
- org.jenkins-ci.plugins:Parameterized-Remote-Trigger (Maven): affected all versions; fixed in 3.1.4

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

## Sources

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

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