Skip to content

Path traversal in Jenkins Git Mercurial and Repo Plugins

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

Package

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

Affected versions

<= 4.11.1

Patched versions

4.11.2
maven org.jenkins-ci.plugins:mercurial (Maven)
<= 2.16
2.16.1
maven org.jenkins-ci.plugins:repo (Maven)
<= 1.14.0
1.15.0

Description

Jenkins SCMs support a number of different URL schemes, including local file system paths (e.g. using file: URLs).

Historically in Jenkins, only agents checked out from SCM, and if multiple projects share the same agent, there is no expected isolation between builds besides using different workspaces unless overridden. Some Pipeline-related features check out SCMs from the Jenkins controller as well.

This allows attackers able to configure pipelines to check out some SCM repositories stored on the Jenkins controller’s file system using local paths as SCM URLs, obtaining limited information about other projects' SCM contents.

References

Published by the National Vulnerability Database May 17, 2022
Published to the GitHub Advisory Database May 18, 2022
Reviewed Jun 2, 2022
Last updated Dec 6, 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
None
Scope
Unchanged
Confidentiality
High
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:N/UI:N/S:U/C:H/I:N/A:N

EPSS score

0.135%
(49th percentile)

Weaknesses

CVE ID

CVE-2022-30947

GHSA ID

GHSA-84cm-vjwm-m979

Source code

Credits

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