Skip to content

Missing permission check in Jenkins Pipeline Maven Integration Plugin allow capturing credentials

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

Package

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

Affected versions

< 3.8.3

Patched versions

3.8.3

Description

Pipeline Maven Integration Plugin 3.8.2 and earlier does not perform a permission check in a method implementing form validation.

This allows users with Overall/Read access to Jenkins to connect to an attacker-specified JDBC URL using attacker-specified credentials IDs obtained through another method, potentially capturing credentials stored in Jenkins.

Additionally, this form validation method does not require POST requests, resulting in a cross-site request forgery (CSRF) vulnerability.

Pipeline Maven Integration Plugin 3.8.3 requires POST requests and Job/Configure permission for the affected form validation method.

References

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

Severity

High

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
High
Integrity
Low
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.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N

EPSS score

0.065%
(30th percentile)

Weaknesses

CVE ID

CVE-2020-2234

GHSA ID

GHSA-mrr8-fcg7-p2wg

Source code

Credits

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