# CVE-2020-2132: Password stored in plain text by Parasoft Environment Manager Plugin

> Attackers with Extended Read permission or master file system access can view unencrypted passwords stored in Jenkins job configuration files.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Feb 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-gmg2-3w6v-945p

## What is CVE-2020-2132?

CVE-2020-2132 is a medium-severity vulnerability in Jenkins Parasoft Environment Manager Plugin, published on 12 Feb 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Jenkins Parasoft Environment Manager Plugin 2.14 and earlier stores a password unencrypted in job config.xml files on the Jenkins master where it can be viewed by users with Extended Read permission, or access to the master file system.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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

2 open source packages ship an affected version, including com.parasoft:environment-manager. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.parasoft:environment-manager` | Maven | All versions | 2.15 |
| `com.parasoft:environment-manager` | Maven | All versions | 2.15 |

Products: Jenkins Parasoft Environment Manager.

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

Upgrade com.parasoft:environment-manager to 2.15 or later.

## Is CVE-2020-2132 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-2132 is a medium-severity vulnerability in Jenkins Parasoft Environment Manager Plugin, published on 12 Feb 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-2132 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.parasoft:environment-manager (Maven): affected all versions; fixed in 2.15
- com.parasoft:environment-manager (Maven): affected all versions; fixed in 2.15

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

## Sources

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

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