# CVE-2020-2151: Jenkins Quality Gates Plugin transmits credentials in plain text during configuration

> Attackers can view Jenkins Quality Gates Plugin credentials in plain text via the global configuration form, exposing sensitive authentication data.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Mar 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-gvcj-72h4-8xm9

## What is CVE-2020-2151?

CVE-2020-2151 is a medium-severity vulnerability in Jenkins Quality Gates Plugin, published on 9 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Jenkins Quality Gates Plugin 2.5 and earlier transmits configured credentials in plain text as part of its global Jenkins configuration form, potentially resulting in their exposure.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:quality-gates` | Maven | All versions to 2.5 | None |
| `org.jenkins-ci.plugins:quality-gates` | Maven | All versions to 2.5 | None |

Products: Jenkins Quality Gates.

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

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

## Is CVE-2020-2151 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-2151 is a medium-severity vulnerability in Jenkins Quality Gates Plugin, published on 9 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-2151 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:quality-gates (Maven): affected all versions up to 2.5; no fix listed
- org.jenkins-ci.plugins:quality-gates (Maven): affected all versions up to 2.5; 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-2020-2151/ (Markdown: https://insights.sbomify.com/CVE-2020-2151/index.md)
```

## Sources

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

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