CVE-2019-1003030: Jenkins Matrix Project Plugin Remote Code Execution Vulnerability
A sandbox bypass vulnerability exists in Jenkins Pipeline: Groovy Plugin 2.63 and earlier in pom.xml, src/main/java/org/jenkinsci/plugins/workflow/cps/CpsGroovyShell.java that allows attackers able to control pipeline scripts to execute arbitrary code on the Jenkins master JVM.
Other sources
Jenkins Matrix Project plugin contains a vulnerability which can allow users to escape the sandbox, opening opportunity to perform remote code execution.
— CISA
The Jenkins Pipeline: Groovy sandbox protection could be circumvented during parsing, compilation, and script instantiation by providing a crafted Groovy script.
This allowed users able to control the contents of a pipeline to bypass the sandbox protection and execute arbitrary code on the Jenkins master.
Pipeline: Groovy Plugin now uses Script Security APIs that apply sandbox protection during these phases.
External Reference:
https://jenkins.io/security/advisory/2019-03-06/#SECURITY-1336%20(2)
— Red Hat
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
maven/org.jenkins-ci.plugins.workflow:workflow-cpsto a version that resolves this vulnerability.Fixed in 2.64 - Upgrade
Upgrade
redhat/jenkins-plugin-workflow-cpsto a version that resolves this vulnerability.Fixed in 2.64
Event History
Frequently Asked Questions
What is the severity of CVE-2019-1003030?
CVE-2019-1003030 is considered a high severity vulnerability due to its potential for remote code execution.
What versions are affected by CVE-2019-1003030?
CVE-2019-1003030 affects Jenkins Pipeline: Groovy Plugin versions up to and including 2.63.
How do I fix CVE-2019-1003030?
To fix CVE-2019-1003030, upgrade Jenkins Pipeline: Groovy Plugin to version 2.64 or later.
What impact does CVE-2019-1003030 have on Jenkins users?
CVE-2019-1003030 can allow users to escape the Jenkins sandbox, leading to potential unauthorized code execution.
Is there a workaround for CVE-2019-1003030?
There is no known workaround for CVE-2019-1003030; upgrading to the secure version is the recommended action.