First published: Mon Mar 20 2017(Updated: )
It was found that the use of Pipeline: Classpath Step Jenkins plugin enables a bypass of the Script Security sandbox for users with SCM commit access, as well as users with e.g. Job/Configure permission in Jenkins.
Credit: secalert@redhat.com secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
maven/cprice404:pipeline-classpath | =0.1.0 | |
Jenkins Pipeline | =0.1.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-2650 has a medium severity rating that indicates potential risks due to bypassing the Script Security sandbox in Jenkins.
To fix CVE-2017-2650, you should update the Jenkins Pipeline Classpath Step plugin to version 0.1.1 or later.
Users with SCM commit access and users with Job/Configure permissions in Jenkins are affected by CVE-2017-2650.
The impact of CVE-2017-2650 is that it allows unauthorized access to bypass the Script Security sandbox, potentially leading to execution of untrusted scripts.
Jenkins versions using the Pipeline Classpath Step plugin version 0.1.0 are vulnerable to CVE-2017-2650.