Skip to content

Passwords transmitted in plain text by Jenkins ReadyAPI Functional Testing Plugin

Moderate severity GitHub Reviewed Published May 24, 2022 to the GitHub Advisory Database • Updated Oct 26, 2023

Package

maven org.jenkins-ci.plugins:soapui-pro-functional-testing (Maven)

Affected versions

<= 1.5

Patched versions

1.6

Description

ReadyAPI Functional Testing Plugin stores project passwords in job config.xml files on the Jenkins controller as part of its configuration.

While these passwords are stored encrypted on disk since ReadyAPI Functional Testing Plugin 1.4, they are transmitted in plain text as part of the global configuration form by ReadyAPI Functional Testing Plugin 1.5 and earlier. These passwords can be viewed by attackers with Extended Read permission.

This only affects Jenkins before 2.236, including 2.235.x LTS, as Jenkins 2.236 introduces a security hardening that transparently encrypts and decrypts data used for a Jenkins password form field.

References

Published by the National Vulnerability Database Sep 1, 2020
Published to the GitHub Advisory Database May 24, 2022
Reviewed Dec 20, 2022
Last updated Oct 26, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

EPSS score

0.054%
(23rd percentile)

Weaknesses

CVE ID

CVE-2020-2251

GHSA ID

GHSA-q4qq-8q2r-g2f2

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.