Skip to content

Credentials transmitted in plain text by Jenkins Logstash Plugin

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

Package

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

Affected versions

< 2.3.2

Patched versions

2.3.2

Description

Logstash Plugin stores credentials in its global configuration file jenkins.plugins.logstash.LogstashConfiguration.xml on the Jenkins controller as part of its configuration.

While the credentials are stored encrypted on disk, they are transmitted in plain text as part of the configuration form by Logstash Plugin 2.3.1 and earlier. This can result in exposure of the credential through browser extensions, cross-site scripting vulnerabilities, and similar situations.

Logstash Plugin 2.3.2 transmits the credentials in its global configuration encrypted.

References

Published by the National Vulnerability Database Mar 9, 2020
Published to the GitHub Advisory Database May 24, 2022
Reviewed Jan 14, 2023
Last updated Dec 14, 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.090%
(40th percentile)

Weaknesses

CVE ID

CVE-2020-2143

GHSA ID

GHSA-5pg8-f89x-wjcx

Source code

Credits

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