CVE-2020-2250 json
Passwords stored in plain text by Jenkins ReadyAPI Functional Testing Plugin
published 6y ago modified 4mo ago also GHSA-ccwp-633j-g29v , EUVD-2022-3564
- cvss
- 6.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 50%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- maven org.jenkins-ci.plugins:soapui-pro-functional-testing 1.4
Is CVE-2020-2250 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.63% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:P/I:N/A:N |
| GitHub | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.jenkins-ci.plugins:soapui-pro-functional-testing | <1.4 |
1.4 |
Affected products
- Jenkins project Jenkins SoapUI Pro Functional Testing Plugin
Classification
References
- jenkins.io /security/advisory/2020-09-01/#SECURITY-1631%20%281%29
-
openwall.com
/lists/oss-security/2020/09/01/3
mailing-list, web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-2250
advisory
-
github.com
/jenkinsci/soapui-pro-functional-testing-plugin
package
-
jenkins.io
/security/advisory/2020-09-01/#SECURITY-1631%20(1)
web
Sources
- CVE List CVE-2020-2250
- GitHub Advisory GHSA-ccwp-633j-g29v
- NVD CVE-2020-2250
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.