Path traversal in Jenkins Mercurial Plugin
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
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2022-30948US | high7.5 | — | ||
Jenkins Mercurial Plugin 2.16 and earlier allows attackers able to configure pipelines to check out some SCM repositories stored on the Jenkins controller's file system using local… | ||||
references
External citations — patches, advisories, analysis.
- http://www.openwall.com/lists/oss-security/2022/05/17/8WEB
- https://github.com/jenkinsci/mercurial-pluginPACKAGE
- https://github.com/jenkinsci/mercurial-plugin/commit/b995436e560b01818f5d9e9920990370cc575341WEB
- https://nvd.nist.gov/vuln/detail/CVE-2022-30948ADVISORY
- https://www.jenkins.io/security/advisory/2022-05-17/#SECURITY-2478WEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan