Jenkins Pipeline Declarative Plugin sandbox bypass vulnerability
Jenkins Script Security sandbox protection could be circumvented during the script compilation phase by applying AST transforming annotations such as `@Grab` to source code elements. Both the pipeline validation REST APIs and actual script/pipeline execution are affected. This allowed users with Overall/Read permission, or able to control Jenkinsfile or sandboxed Pipeline shared library contents in SCM, to bypass the sandbox protection and execute arbitrary code on the Jenkins controller. All known unsafe AST transformations in Groovy are now prohibited in sandboxed scripts.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2019-1003002US | high8.8 | Exploit | ||
A sandbox bypass vulnerability exists in Pipeline: Declarative Plugin 1.3.3 and earlier in pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/… | ||||
references
External citations — patches, advisories, analysis.
- http://packetstormsecurity.com/files/152132/Jenkins-ACL-Bypass-Metaprogramming-Remote-Code-Execution.htmlWEB
- http://www.rapid7.com/db/modules/exploit/multi/http/jenkins_metaprogrammingWEB
- https://access.redhat.com/errata/RHBA-2019:0326WEB
- https://access.redhat.com/errata/RHBA-2019:0327WEB
- https://github.com/jenkinsci/pipeline-model-definition-plugin/commit/083abd96e68fd89f556a0cd53db5f878dbf09b92WEB
- https://jenkins.io/security/advisory/2019-01-08/#SECURITY-1266WEB
- https://nvd.nist.gov/vuln/detail/CVE-2019-1003002ADVISORY
- https://www.exploit-db.com/exploits/46572WEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan