# CVE-2020-2250: Passwords stored in plain text by Jenkins ReadyAPI Functional Testing Plugin

> Attackers with Extended Read permission or file system access can view unencrypted project passwords stored in Jenkins SoapUI Pro plugin 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:** 1 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-ccwp-633j-g29v

## What is CVE-2020-2250?

CVE-2020-2250 is a medium-severity vulnerability in Jenkins SoapUI Pro Functional Testing 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 SoapUI Pro Functional Testing Plugin 1.3 and earlier stores project passwords unencrypted in job config.xml files on the Jenkins controller where they can be viewed by attackers with Extended Read permission, or access to the Jenkins controller file system.

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

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

2 open source packages ship an affected version, including org.jenkins-ci.plugins:soapui-pro-functional-testing. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:soapui-pro-functional-testing` | Maven | All versions | 1.4 |
| `org.jenkins-ci.plugins:soapui-pro-functional-testing` | Maven | All versions | 1.4 |

Products: Jenkins Soapui Pro Functional Testing.

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

Upgrade org.jenkins-ci.plugins:soapui-pro-functional-testing to 1.4 or later.

## Is CVE-2020-2250 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-2250 is a medium-severity vulnerability in Jenkins SoapUI Pro Functional Testing 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-2250 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:soapui-pro-functional-testing (Maven): affected all versions; fixed in 1.4
- org.jenkins-ci.plugins:soapui-pro-functional-testing (Maven): affected all versions; fixed in 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-2250/ (Markdown: https://insights.sbomify.com/CVE-2020-2250/index.md)
```

## Sources

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

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