CVE-2019-1003030: Jenkins Matrix Project Plugin Remote Code Execution Vulnerability
First published: Fri Mar 08 2019(Updated: )
Jenkins Matrix Project plugin contains a vulnerability which can allow users to escape the sandbox, opening opportunity to perform remote code execution.
Credit: jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| redhat/jenkins-plugin-workflow-cps | <2.64 | 2.64 |
| maven/org.jenkins-ci.plugins.workflow:workflow-cps | <2.64 | 2.64 |
| Jenkins Matrix Project | ||
| Jenkins Pipeline | <=2.63 | |
| Red Hat OpenShift Container Platform | =3.11 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://nvd.nist.gov/vuln/detail/CVE-2019-1003030
- https://access.redhat.com/errata/RHSA-2019:0739
- https://jenkins.io/security/advisory/2019-03-06/#SECURITY-1336%20(2)
- http://packetstormsecurity.com/files/159603/Jenkins-2.63-Sandbox-Bypass.html
- http://www.securityfocus.com/bid/107476
- https://github.com/advisories/GHSA-r6mc-mrvr-23cr (Advisory)
- https://jenkins.io/security/advisory/2019-03-06/#SECURITY-1336%20%282%29
- https://jenkins.io/security/advisory/2019-03-06/#SECURITY-1336%20(2
- https://bugzilla.redhat.com/show_bug.cgi?id=1690665
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.
- agent/type
- agent/references
- agent/description
- agent/weakness
- agent/title
- agent/author
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2019-1003030
- agent/software-canonical-lookup
- collector/github-advisory-latest
- source/GitHub
- alias/GHSA-r6mc-mrvr-23cr
- collector/github-advisory
- agent/severity
- agent/first-publish-date
- agent/trending
- agent/source
- collector/mitre-cve
- source/MITRE
- agent/event
- agent/last-modified-date
- exploited/true
- collector/cisa-known-exploited
- source/CISA
- agent/software-canonical-lookup-request
- agent/softwarecombine
- agent/tags
- collector/nvd-index
- collector/nvd-cve
- source/NVD
- collector/nvd-api
- package-manager/redhat
- package-manager/maven
- vendor/jenkins
- canonical/jenkins matrix project
- canonical/jenkins pipeline
- version/jenkins pipeline/2.63
- vendor/redhat
- canonical/red hat openshift container platform
- version/red hat openshift container platform/3.11