How severe is CVE-2022-30949?

CVE-2022-30949 has a CVSS score of 3.7/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2022-30949?

CVE-2022-30949 affects the following packages: org.jenkins-ci.plugins:repo (Maven), org.jenkins-ci.plugins:mercurial (Maven), org.jenkins-ci.plugins:git (Maven). Ecosystems affected: Maven.

How do I fix CVE-2022-30949?

Update org.jenkins-ci.plugins:repo to 1.14.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-30949 is resolved across your whole dependency graph.

How do I detect CVE-2022-30949 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:repo, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-30949 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2022-30949 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-30949 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2022-30949?

CVE-2022-30949 has an EPSS (Exploit Prediction Scoring System) score of 1.0%, placing it in the 64th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was CVE-2022-30949 published, and has it been updated?

CVE-2022-30949 was published on May 18, 2022 and was last updated on February 16, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

LOW severity

CVE-2022-30949 — repo

LOWFix: jenkinsci/git-plugin@b295606

CVE-2022-30949 is a low-severity (CVSS 3.7) vulnerability in org.jenkins-ci.plugins:repo. A fix is available for org.jenkins-ci.plugins:repo — see the affected versions and patch details below.

Path traversal in Jenkins REPO Plugin

Published

May 18, 2022

Updated

Feb 16, 2024

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs64th percentile — riskier than 64% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected

☕org.jenkins-ci.plugins:repo☕org.jenkins-ci.plugins:mercurial☕org.jenkins-ci.plugins:git

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.plugins:repo`	all versions	1.14.1`org.jenkins-ci.plugins:repo:1.14.1`
☕Maven	`org.jenkins-ci.plugins:mercurial`	all versions	2.16.1`org.jenkins-ci.plugins:mercurial:2.16.1`
☕Maven	`org.jenkins-ci.plugins:git`	all versions	4.11.2`org.jenkins-ci.plugins:git:4.11.2`

Affected Products

1 product · 1 configurations

Application

repojenkins

< 1.15.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:repo, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:repo to 1.14.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-30949 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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 o

O3 Security · Impact-Aware SCA

Is CVE-2022-30949 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

3.7/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

May 18, 2022

Last updated

Feb 16, 2024

Identifiers

CVE-2022-30949

References

Advisorynvd.nist.gov · CVE 2022 30949 Webgithub.com · b295606e0b865c298fde27bea14f9b7535a976e6 Webgithub.com · 55904fbb8c9d3e0b36fc26330374904cb68e8758 Webgithub.com · 8c9cbb88baffc64d1b63183235eb86c773108235 Webjenkins.io · 2022 05 17 Webopenwall.com Packagegithub.com · repo plugin

Related vulnerabilities

Also affects repo

This CVE is low severity; 2 of 2 other CVEs affecting repo are rated as high or higher (top: high).

CVE-2022-43415CVE-2022-30947

Also affects mercurial

This CVE is low severity; 5 of 5 other CVEs affecting mercurial are rated as high or higher (top: moderate).

CVE-2022-43410CVE-2020-2306CVE-2020-2305CVE-2022-30948CVE-2018-1000112

Also affects git

This CVE is low severity; 1 of 1 other CVE affecting git is rated as high or higher (top: moderate).

CVE-2022-38663

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedFeb 16, 2024

CVE-2022-30949 — repo

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2022-30949 in your dependencies?