CVE-2022-36882: Lack of authentication mechanism in Jenkins Git Plugin webhook

CVE-2022-36882 · Severity: low · CVSS 3.1 · Published 2022-07-28

Lack of authentication mechanism in Jenkins Git Plugin webhook

Technologies: org.jenkins-ci.plugins:git (Maven). Vendors: Maven.

Quick answers

Is CVE-2022-36882 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2022-36882 being exploited in the wild.
How severe is CVE-2022-36882?
Low severity, with a CVSS score of 3.1, published 28 July 2022.
Which products and versions are affected?
org.jenkins-ci.plugins:git (Maven) ECOSYSTEM:introduced=0,fixed=4.11.4.
Is there a fix for CVE-2022-36882?
Yes. org.jenkins-ci.plugins:git (Maven): upgrade to 4.11.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2022-36882?
Check whether you run org.jenkins-ci.plugins:git (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • org.jenkins-ci.plugins:git (Maven): upgrade to 4.11.4 or later
    # set org.jenkins-ci.plugins:git to 4.11.4 in your pom.xml or build.gradle

Affected products

  • org.jenkins-ci.plugins:git (Maven) ECOSYSTEM:introduced=0,fixed=4.11.4

Identifiers

  • CVE-2022-36882
  • GHSA-8xwj-2wgh-gprh

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.