Skip to content

CSRF vulnerability and in Jenkins OWASP Dependency-Track Plugin allow capturing credentials

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

Package

maven org.jenkins-ci.plugins:dependency-track (Maven)

Affected versions

<= 3.1.0

Patched versions

3.1.1

Description

Jenkins OWASP Dependency-Track Plugin 3.1.0 and earlier does not perform permission checks in several HTTP endpoints.

This allows attackers with Overall/Read permission to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing "Secret text" credentials stored in Jenkins. If no credentials ID is specified, the globally configured credential is used, if set up, and can likewise be captured.

Additionally, these HTTP endpoints do not require POST requests, resulting in a cross-site request forgery (CSRF) vulnerability.

Jenkins OWASP Dependency-Track Plugin 3.1.1 requires POST requests and appropriate permissions for the affected HTTP endpoints.

References

Published by the National Vulnerability Database Mar 30, 2021
Published to the GitHub Advisory Database May 24, 2022
Reviewed Dec 15, 2022
Last updated Dec 7, 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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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:N/UI:R/S:U/C:H/I:H/A:H

EPSS score

0.088%
(39th percentile)

Weaknesses

CVE ID

CVE-2021-21633

GHSA ID

GHSA-v7xh-h48c-xw5f

Source code

Credits

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