dbcve.org
MercurialApplication · Jenkins

CVE-2022-30948

HIGH · 7.5 CVSS v3.1 Published 2022-05-17
Fix available
A fix is available. Upgrade to 2.16.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Jenkins Mercurial Plugin before 2.17 does not properly restrict local file system path access when processing SCM URLs. Attackers with pipeline configuration permissions can use local paths (e.g., /path/to/repo) as SCM URLs to read SCM contents from other projects' repositories stored on the Jenkins controller, bypassing intended project-based access controls.

MitigationUpgrade Jenkins Mercurial Plugin to version 2.17 or later, which properly validates and restricts path traversal when processing local paths as SCM URLs.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MercurialApplication
Affected:< 2.16.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Jenkins Mercurial Plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed and look for 'Mercurial Plugin' in the list. Alternatively, check the plugin directory (typically $JENKINS_HOME/plugins/) for the mercurial plugin folder.
    Affected if The plugin is present in the Jenkins environment
  2. Check installed Mercurial Plugin version
    In Manage Jenkins > Manage Plugins > Installed, find the Mercurial Plugin and note the version number displayed. Compare this version against the affected range (versions before 2.17, specifically below 2.16.1).
    Affected if The installed version is 2.16.1 or lower (any version less than 2.17)
  3. Identify users with pipeline configuration permissions
    Navigate to Manage Jenkins > Manage Users or check configured security realm and authorization matrix. Look for users or groups granted the 'Pipeline' or 'Job/Configure' permission that could create or modify pipeline definitions.
    Affected if Non-admin users have permissions to configure pipeline SCM URLs
  4. Review existing pipeline SCM configurations for local paths
    Examine configured pipelines (in Job configuration or Jenkinsfile definitions) that use the Mercurial source. Check the Repository URL field for local file system paths (paths starting with /, or relative paths pointing to local directories).
    Affected if Any pipeline is configured with a local file system path as the Mercurial repository URL

A user is affected if the Jenkins Mercurial Plugin version is 2.16.1 or lower AND users with pipeline configuration permissions exist in the environment, regardless of whether local paths are currently in use.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.16.1 or later
Fixed in 2.16.1
Interim mitigation

Upgrade Jenkins Mercurial Plugin to version 2.17 or later, which properly validates and restricts path traversal when processing local paths as SCM URLs.

Recommended fix High confidence

Jenkins Mercurial Plugin 2.16.1

  1. 1. Navigate to the Jenkins dashboard
  2. 2. Go to Manage Jenkins > Manage Plugins
  3. 3. Click on the 'Installed' tab
  4. 4. Find 'Mercurial Plugin' in the list
  5. 5. If the plugin shows version 2.16 or earlier, click 'Update now' to upgrade to version 2.16.1 or later
  6. 6. Restart Jenkins to complete the plugin update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mercurial Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-30948 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-30948 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data