CVE-2022-30948
Path traversal in Jenkins Mercurial Plugin
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 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
- High
- Integrity
- None
- Availability
- None
Exploit likelihood
What each source reports
NVD Score used
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 paths as SCM URLs, obtaining limited information about other projects' SCM contents.
- Record
CVE-2022-30948- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 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 paths as SCM URLs, obtaining limited information about other projects' SCM contents.
- Record
CVE-2022-30948- Updated
- 2026-11-02
EUVDEUVD-2022-2520 No score
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 paths as SCM URLs, obtaining limited information about other projects' SCM contents.
- Record
EUVD-2022-2520- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-5786-3qjg-mr88
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
- Record
GHSA-5786-3qjg-mr88- 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
OSV
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 paths as SCM URLs, obtaining limited information about other projects' SCM contents.
- Record
CVE-2022-30948- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N - Updated
- 2026-11-02
OSVGHSA-5786-3qjg-mr88
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
- Record
GHSA-5786-3qjg-mr88- 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
OSVRHSA-2023:0017
Red Hat Security Advisory: OpenShift Container Platform 4.8.56 packages and security update
- Record
RHSA-2023:0017- CVSS 3.1
- 8.8 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
org.jenkins-ci.plugins:mercurialMaven |
through 2.16 | 2.16.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 |
jenkinsRed Hat:openshift:4.8::el8 From an advisory covering 16 CVEs |
before 0:2.361.1.1672840472-1.el8 | 0:2.361.1.1672840472-1.el8 |
jenkins-2-pluginsRed Hat:openshift:4.8::el8 From an advisory covering 16 CVEs |
before 0:4.8.1672842762-1.el8 | 0:4.8.1672842762-1.el8 |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected, facts | ||
| 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-30948 is a high vulnerability (CVSS 7.5) in Jenkins Mercurial, published May 17, 2022. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 1.52%, the 74th percentile. Fixed in org.jenkins-ci.plugins:mercurial 2.16.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-30948
github.com/jenkinsci/mercurial-plugin/commit/b995436e560b01818f5d9e9920990370cc575341
Show 71 moreShow less
access.redhat.com/errata/RHSA-2023:0017
bugzilla.redhat.com/show_bug.cgi?id=2074855
security.access.redhat.com/data/csaf/v2/advisories/2023/rhsa-2023_0017.json
cve.org/CVERecord?id=CVE-2022-2048
Left out here: 8 versions. The JSON record has them.