Skip to content

Passwords transmitted in plain text by Jenkins Stash Branch Parameter Plugin

Low severity GitHub Reviewed Published May 24, 2022 to the GitHub Advisory Database • Updated Jan 28, 2023

Package

maven org.jenkins-ci.plugins:StashBranchParameter (Maven)

Affected versions

<= 0.3.0

Patched versions

None

Description

Stash Branch Parameter Plugin stores Stash API passwords in its global configuration file org.jenkinsci.plugins.StashBranchParameter.StashBranchParameterDefinition.xml on the Jenkins controller as part of its configuration.

While the password is stored encrypted on disk, it is transmitted in plain text as part of the configuration form by Stash Branch Parameter Plugin 0.3.0 and earlier. This can result in exposure of the password through browser extensions, cross-site scripting vulnerabilities, and similar situations.

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 Jul 2, 2020
Published to the GitHub Advisory Database May 24, 2022
Reviewed Dec 29, 2022
Last updated Jan 28, 2023

Severity

Low

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
High
Privileges required
None
User interaction
Required
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:H/PR:N/UI:R/S:U/C:L/I:N/A:N

EPSS score

0.084%
(37th percentile)

Weaknesses

CVE ID

CVE-2020-2210

GHSA ID

GHSA-3f82-v3qw-53q7

Source code

Credits

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