CVE-2022-25180: Jenkins Pipeline: Groovy Plugin has Insufficiently Protected Credentials

CVE-2022-25180 · Severity: low · CVSS 3.1 · Published 2022-02-16

Jenkins Pipeline: Groovy Plugin has Insufficiently Protected Credentials

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

Quick answers

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

Affected products

  • org.jenkins-ci.plugins.workflow:workflow-cps (Maven) ECOSYSTEM:introduced=0,fixed=2656.vf7a_e7b_75a_457

Identifiers

  • CVE-2022-25180
  • GHSA-qv6q-x9vr-w7j3

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