dbcve.org
Git ClientApplication · Jenkins

CVE-2022-36881

HIGH · 8.1 CVSS v3.1 Published 2022-07-27
Fix available
A fix is available. Upgrade to after 3.11.0 or later.
See remediation →
90/100
Remediation priority · Urgent
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 client Plugin 3.11.0 and earlier does not perform SSH host key verification when connecting to Git repositories via SSH, enabling man-in-the-middle attacks.

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 Git client Plugin versions 3.11.0 and earlier fail to perform SSH host key verification when connecting to Git repositories via SSH. This allows attackers to intercept connections between Jenkins and Git servers through man-in-the-middle attacks, potentially stealing credentials or injecting malicious code into the repository workflow.

MitigationUpgrade Jenkins Git client Plugin to version 3.11.1 or later which implements proper SSH host key verification. Until upgraded, ensure Git SSH connections only occur over trusted networks or implement additional network-level protections.

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
Git ClientApplication
Affected:<= 3.11.0

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Determine installed Jenkins Git client Plugin version
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, search for 'Git client Plugin', and note the version number listed.
    Affected if The installed version is 3.11.0 or earlier.
  2. Identify Git repositories using SSH URLs
    Review Jenkins job configurations and any pipelines or freestyle projects that use Git. Check for repository URLs starting with 'ssh://' or using the Git SSH protocol format.
    Affected if Any Jenkins job or pipeline is configured to fetch from a Git repository using an SSH URL (not HTTPS or HTTP).
  3. Check for SSH host key verification configuration
    Inspect the Jenkins Git client Plugin global configuration at Manage Jenkins > Configure System > Git > Git Installations or look for SSH credentials/configuration in the advanced settings.
    Affected if SSH host key verification is disabled, not configured, or the plugin version lacks host key verification capability (versions 3.11.0 and earlier).

You are affected if the Jenkins Git client Plugin version is 3.11.0 or earlier and any job uses SSH-based Git URLs without proper host key verification 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 a release after 3.11.0
Interim mitigation

Upgrade Jenkins Git client Plugin to version 3.11.1 or later which implements proper SSH host key verification. Until upgraded, ensure Git SSH connections only occur over trusted networks or implement additional network-level protections.

Recommended fix Moderate confidence

Git client Plugin 3.11.1 or later

  1. Navigate to Jenkins dashboard
  2. Go to Manage Jenkins > Manage Plugins
  3. Select the 'Installed' tab
  4. Locate 'Git client' plugin in the list
  5. If an update is available, check the update box and click 'Update'
  6. Restart Jenkins if required for the update to take effect
  7. Alternatively, manually download the updated .hpi file from the Jenkins plugin repository and upload it via 'Advanced' > 'Upload Plugin'

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

Fix this in Git Client Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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