Path traversal in Jenkins Git Mercurial and Repo Plugins
Jenkins project Jenkins Git Plugin
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.jenkins-ci.plugins:git Maven |
|
|
| org.jenkins-ci.plugins:mercurial Maven |
|
|
| org.jenkins-ci.plugins:repo |
Jenkins project Jenkins Git Plugin
| Product | Affected | Fixed in |
|---|---|---|
| org.jenkins-ci.plugins:git Maven |
|
|
| org.jenkins-ci.plugins:mercurial Maven |
|
|
| org.jenkins-ci.plugins:repo |
|
|
Jenkins Git Plugin 4.11.1 and earlier 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.
From the CVE record · jenkins
Jenkins Git Plugin 4.11.1 and earlier allows attackers who can configure pipelines to use local paths as SCM URLs. They can check out some repositories stored on the Jenkins controller’s file system and obtain limited information about other projects’ SCM contents.
Teams running Jenkins with Maven packages org.jenkins-ci.plugins:git below 4.11.2, org.jenkins-ci.plugins:mercurial below 2.16.1, or org.jenkins-ci.plugins:repo below 1.15.0 should check their installations.