CVE-2022-30949
Path traversal in Jenkins REPO Plugin
Jenkins REPO Plugin 1.14.0 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.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
Exploit likelihood
What each source reports
NVD Score used
Jenkins REPO Plugin 1.14.0 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.
- Record
CVE-2022-30949- CVSS 3.1
- 5.3 Medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N - CVSS 2.0
- 5.0 Medium
AV:N/AC:L/Au:N/C:P/I:N/A:N - Updated
- 2026-11-02
CVE List No score
Jenkins REPO Plugin 1.14.0 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.
- Record
CVE-2022-30949- Updated
- 2026-11-02
EUVDEUVD-2022-3239 No score
Jenkins REPO Plugin 1.14.0 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.
- Record
EUVD-2022-3239- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-8vfc-fcr2-47pj
Path traversal in Jenkins REPO 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.
- Record
GHSA-8vfc-fcr2-47pj- CVSS 3.1
- 3.7 Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N - Weakness
- CWE-22
- Updated
- 2026-11-02
OSVGHSA-8vfc-fcr2-47pj
Path traversal in Jenkins REPO 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.
- Record
GHSA-8vfc-fcr2-47pj- CVSS 3.1
- 3.7 Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N - Weakness
- CWE-22
- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
org.jenkins-ci.plugins:repoMaven |
before 1.14.1 | 1.14.1 |
org.jenkins-ci.plugins:mercurialMaven |
before 2.16.1 | 2.16.1 |
org.jenkins-ci.plugins:gitMaven |
before 4.11.2 | 4.11.2 |
org.jenkins-ci.plugins:repoMaven |
before 1.14.1, plus listed versions 1.01.11.10.01.10.11.10.2 Show 21 moreShow less1.10.31.10.41.10.51.10.61.10.71.11.01.11.11.12.01.12.11.12.21.13.01.14.01.21.2.11.31.51.61.71.7.11.8.01.9.0 |
1.14.1 |
org.jenkins-ci.plugins:mercurialMaven |
before 2.16.1, plus listed versions 1.371.381.391.401.41 Show 45 moreShow less1.421.431.441.451.461.471.481.48-beta-11.491.501.50-beta-11.50-beta-21.50.11.511.51-beta-11.51-beta-21.51-beta-31.521.531.541.551.561.571.581.58-beta-11.591.601.612.02.0-alpha-12.0-alpha-42.0-beta-12.12.102.10.12.112.122.132.142.152.15.12.15.22.162.22.3 |
2.16.1 |
org.jenkins-ci.plugins:gitMaven |
before 4.11.2, plus listed versions 1.2.01.3.01.4.01.5.01.6.0-beta-1 Show 45 moreShow less2.02.0-beta-22.0-beta-32.0.12.0.22.0.32.0.42.1.02.2.02.2.12.2.102.2.112.2.122.2.22.2.32.2.42.2.52.2.62.2.72.2.82.2.92.32.3-beta-12.3-beta-22.3-beta-32.3-beta-42.3.12.3.22.3.32.3.42.3.52.4.02.4.12.4.22.4.32.4.42.5.02.5.0-beta12.5.0-beta22.5.0-beta32.5.0-beta42.5.0-beta52.5.12.5.22.5.3 |
4.11.2 |
History
| Recorded | Changed | Sources |
|---|---|---|
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2022-30949 is a medium vulnerability (CVSS 5.3) in Jenkins Repo, published May 17, 2022. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 1.05%, the 64th percentile. Fixed in org.jenkins-ci.plugins:repo 1.14.1.
References
jenkins.io/security/advisory/2022-05-17
openwall.com/lists/oss-security/2022/05/17/8
nvd.nist.gov/vuln/detail/CVE-2022-30949
github.com/jenkinsci/repo-plugin/commit/8c9cbb88baffc64d1b63183235eb86c773108235
Left out here: 108 versions. The JSON record has them.