Skip to content
Fencer Intel
high 8.1

CVE-2022-36881 json

Jenkins Git client plugin 3.11.0 does not perform SSH host key verification

published 4y ago modified 4mo ago also GHSA-cm7j-p8hc-97vj , EUVD-2022-6320

cvss
8.1
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.0%
EPSS 1.0% chance of exploitation in 30 days, percentile 63%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.jenkins-ci.plugins:git-client 3.11.1
  • Jenkins project Jenkins Git client Plugin 3.10.0.1
  • jenkins openshift 4.8 2.361.1.1672840472-1.el8
  • jenkins-2-plugins openshift 4.8 4.8.1672842762-1.el8
  • jenkins-2-plugins openshift 4.9 4.9.1667460322-1.el8
  • jenkins-2-plugins openshift 4.10 4.10.1667388055-1.el8

red hat advisories RHSA-2023:0017RHBA-2022:8582RHSA-2022:7865

Is CVE-2022-36881 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-36881 updated cvss 8.1

jenkins-plugin: Man-in-the-Middle (MitM) in org.jenkins-ci.plugins:git-client

  • Red Hat OpenShift Container Platform 3.11 jenkins-2-plugins
    affected: no fix planned “Will not fix”
  • Red Hat OpenShift Container Platform 4.8 jenkins-2-plugins 4.8.1672842762-1.el8
    fixed: vendor fix RHSA-2023:0017
  • Red Hat OpenShift Container Platform 4.9 jenkins-2-plugins 4.9.1667460322-1.el8
    fixed: vendor fix RHBA-2022:8582
  • Red Hat OpenShift Container Platform 4.10 jenkins-2-plugins 4.10.1667388055-1.el8
    fixed: vendor fix RHSA-2022:7865
  • Red Hat OpenShift Container Platform 4.8 jenkins 2.361.1.1672840472-1.el8 Red Hat OpenShift Container Platform 4.9 python-kubernetes 22.6.0-1.el8, python3-kubernetes 22.6.0-1.el8, jenkins 2.346.1.1667459710-1.el8, python3-kubernetes-tests 22.6.0-1.el8, openshift 4.9.0-202210242129.p0.g9e95cb9.assembly.stream.el7, openshift 4.9.0-202210242129.p0.g9e95cb9.assembly.stream.el8, +6 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.02% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
GitHub 3.1 4.8 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

Affected packages

ecosystem package affected fixed in
maven org.jenkins-ci.plugins:git-client
<3.11.1
3.11.1

Affected products

  • Jenkins project Jenkins Git client Plugin

Classification

Weakness
  • CWE-295 Improper Certificate Validation
  • CWE-322 Key Exchange without Entity Authentication

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.