GitHub Advisoryadvisory · Maven

GHSA-84cm-vjwm-m979 Path traversal in Jenkins Git Mercurial and Repo Plugins

HIGH Published 2022-05-18 Modified 2023-12-06 Official page ↗
Aliases
CVE-2022-30947
Ecosystem
Maven
Packages
org.jenkins-ci.plugins:git, org.jenkins-ci.plugins:mercurial, org.jenkins-ci.plugins:repo
Severity
High
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Weaknesses
CWE-22
Reviewed
2022-06-02

Affected packages

• Maven org.jenkins-ci.plugins:git: < 4.11.2 → fixed in 4.11.2 • Maven org.jenkins-ci.plugins:mercurial: < 2.16.1 → fixed in 2.16.1 • Maven org.jenkins-ci.plugins:repo: < 1.15.0 → fixed in 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.

Related

Alias · CVE (1)

  • CVE-2022-30947 Jenkins Git Plugin 4.11.1 and earlier allows attackers able to configure pipelines to check out some SCM repositories stored on the Jenkins… vulnerability

Weakness · CWE (1)

  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory weakness

References