dbcve.org
GitApplication · Jenkins

CVE-2022-30947

HIGH · 7.5 CVSS v3.1 Published 2022-05-17
Fix available
A fix is available. Upgrade to 4.11.2 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 Git Plugin 4.11.1 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

Jenkins Git Plugin 4.11.1 and earlier contains an information disclosure vulnerability where attackers with pipeline configuration permissions can use local file system paths as SCM URLs to check out repositories stored on the Jenkins controller, potentially accessing limited information from other projects' SCM contents.

MitigationUpgrade Jenkins Git Plugin to version 4.11.2 or later. Additionally, review and restrict pipeline configuration permissions to prevent users from specifying arbitrary local paths as SCM repositories.

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
GitApplication
Affected:< 4.11.2

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. Identify the installed Jenkins Git Plugin version
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'Git plugin', or check the $JENKINS_HOME/plugins/git directory for the plugin version manifest
    Affected if The installed version is 4.11.1 or earlier (versions below 4.11.2)
  2. Audit users with pipeline configuration permissions
    Navigate to Jenkins > Manage Jenkins > Manage Users and cross-reference with pipeline job configuration access via Jenkins > Manage Jenkins > Manage Roles or matrix-based authorization settings
    Affected if There are users other than administrators who can configure pipeline SCM settings
  3. Review pipeline SCM URLs for local file system paths
    Inspect pipeline job configurations (Jenkinsfile or job configuration XML) for any 'checkout' steps or SCM configuration fields that reference local paths such as file:///, /var/lib/jenkins/, or relative paths pointing to the controller filesystem
    Affected if Any pipeline job uses local file system paths as SCM repository URLs

You are affected if the Jenkins Git Plugin version is below 4.11.2 AND users with pipeline configuration permissions exist in the environment, regardless of whether local path SCM URLs are currently configured.

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 4.11.2 or later
Fixed in 4.11.2
Interim mitigation

Upgrade Jenkins Git Plugin to version 4.11.2 or later. Additionally, review and restrict pipeline configuration permissions to prevent users from specifying arbitrary local paths as SCM repositories.

Recommended fix High confidence

Git Plugin 4.11.2

  1. Log in to Jenkins as an administrator
  2. Navigate to Manage Jenkins
  3. Click on Manage Plugins
  4. Select the Updates tab
  5. Locate Git plugin in the available updates list
  6. Check the checkbox next to Git plugin
  7. Click the 'Download now and install after restart' button
  8. After download completes, restart Jenkins to apply the update

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

Fix this in Git Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
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,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-30947 — 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-30947 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