Jenkins Script Security and Pipeline Groovy Plugins Sandbox Bypass
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.jenkins-ci.plugins.workflow:workflow-cps Maven |
|
|
| org.jenkins-ci.plugins:script-security Maven |
|
|
| Product | Affected | Fixed in |
|---|---|---|
| org.jenkins-ci.plugins.workflow:workflow-cps Maven |
|
|
| org.jenkins-ci.plugins:script-security Maven |
|
|
A sandbox bypass vulnerability exists in Pipeline: Groovy Plugin 2.59 and earlier in groovy-sandbox/src/main/java/org/kohsuke/groovy/sandbox/SandboxTransformer.java, groovy-cps/lib/src/main/java/com/cloudbees/groovy/cps/SandboxCpsTransformer.java that allows attackers with Job/Configure permission, or unauthorized attackers with SCM commit privileges and corresponding pipelines based on Jenkinsfiles set up in Jenkins, to execute arbitrary code on the Jenkins master JVM
From the CVE record · mitre
A sandbox bypass in Pipeline: Groovy Plugin 2.59 and earlier allows arbitrary code execution on the Jenkins master JVM. An attacker needs Job/Configure permission, or SCM commit privileges for a pipeline based on a Jenkinsfile configured in Jenkins; Jenkins authentication is not required in the latter case.
Teams running Pipeline: Groovy Plugin 2.59 or earlier, Maven workflow-cps versions before 2.60, or Maven script-security versions before 1.48 should check their installations.