CVE-2022-45379: Whole-script approval in Jenkins Script Security Plugin vulnerable to SHA-1 collisions

CVE-2022-45379 · Severity: low · CVSS 3.1 · Published 2022-11-16

Whole-script approval in Jenkins Script Security Plugin vulnerable to SHA-1 collisions

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

Quick answers

Is CVE-2022-45379 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2022-45379 being exploited in the wild.
How severe is CVE-2022-45379?
Low severity, with a CVSS score of 3.1, published 16 November 2022.
Which products and versions are affected?
org.jenkins-ci.plugins:script-security (Maven) ECOSYSTEM:introduced=0,fixed=1190.v65867a_a_47126.
Is there a fix for CVE-2022-45379?
Yes. org.jenkins-ci.plugins:script-security (Maven): upgrade to 1190.v65867a_a_47126 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2022-45379?
Check whether you run org.jenkins-ci.plugins:script-security (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:script-security (Maven): upgrade to 1190.v65867a_a_47126 or later
    # set org.jenkins-ci.plugins:script-security to 1190.v65867a_a_47126 in your pom.xml or build.gradle

Affected products

  • org.jenkins-ci.plugins:script-security (Maven) ECOSYSTEM:introduced=0,fixed=1190.v65867a_a_47126

Identifiers

  • CVE-2022-45379
  • GHSA-fv42-mx39-6fpw

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