CVE-2018-1000866: Jenkins Script Security and Pipeline Groovy Plugins Sandbox Bypass

Quick answers

Is CVE-2018-1000866 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2018-1000866 being exploited in the wild.

How severe is CVE-2018-1000866?

Low severity, with a CVSS score of 3, published 13 May 2022.

Which products and versions are affected?

org.jenkins-ci.plugins:script-security (Maven) ECOSYSTEM:introduced=0,fixed=1.48; org.jenkins-ci.plugins.workflow:workflow-cps (Maven) ECOSYSTEM:introduced=0,fixed=2.60.

Is there a fix for CVE-2018-1000866?

Yes. org.jenkins-ci.plugins:script-security (Maven): upgrade to 1.48 or later; org.jenkins-ci.plugins.workflow:workflow-cps (Maven): upgrade to 2.60 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Am I affected by CVE-2018-1000866?

Check whether you run org.jenkins-ci.plugins:script-security (Maven) or 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:script-security (Maven): upgrade to 1.48 or later

  # set org.jenkins-ci.plugins:script-security to 1.48 in your pom.xml or build.gradle

• org.jenkins-ci.plugins.workflow:workflow-cps (Maven): upgrade to 2.60 or later

  # set org.jenkins-ci.plugins.workflow:workflow-cps to 2.60 in your pom.xml or build.gradle

Affected products

• org.jenkins-ci.plugins:script-security (Maven) ECOSYSTEM:introduced=0,fixed=1.48
• org.jenkins-ci.plugins.workflow:workflow-cps (Maven) ECOSYSTEM:introduced=0,fixed=2.60

Identifiers

• CVE-2018-1000866
• GHSA-gqhm-4h93-rrhg