CVE-2020-2134: Sandbox bypass vulnerability in Script Security Plugin
Summary
CVE-2020-2134: Sandbox bypass vulnerability in Script Security Plugin. Affects org.jenkins-ci.plugins:script-security versions < 1.7.1. Fixed in 1.7.1. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The Script Security Plugin is a Jenkins plugin that provides a sandbox environment for executing scripts. It allows users to define and run scripts securely within the Jenkins controller JVM. The plugin is widely used in Jenkins installations to enable users to write and execute custom scripts for various tasks.
Vulnerability Detail
The Script Security Plugin version 1.70 and earlier is vulnerable to a sandbox bypass. This vulnerability can be exploited by attackers who are able to specify and run sandboxed scripts. The bypass can be achieved through crafted constructor calls and bodies, as well as crafted method calls on objects that implement GroovyInterceptable. By exploiting this vulnerability, an attacker can execute arbitrary code in the context of the Jenkins controller JVM, potentially leading to unauthorized access, data breaches, or other malicious activities.
How To Fix
Latest published version: 1436.v1082791135e4 as of 22 Oct 2026
Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
1.7.1
This is the first release that contains the fix.
Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
There is no known workaround for this vulnerability. It is recommended to upgrade to the fixed version of the Script Security Plugin as soon as possible.
Conclusion
The Script Security Plugin version 1.70 and earlier is vulnerable to a sandbox bypass, allowing attackers to execute arbitrary code in the context of the Jenkins controller JVM. To mitigate this risk, it is crucial to upgrade to the fixed version of the plugin (1.71 or later). For further assistance or support in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for org.jenkins-ci.plugins:script-security →
FAQ
This vulnerability allows attackers to execute arbitrary code in the context of the Jenkins controller JVM. This can lead to unauthorized access, data breaches, or other malicious activities.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your Jenkins installation is affected by this vulnerability. Simply provide your pom.xml file, and Vulert will analyze it in real-time and alert you if any open-source vulnerabilities, including this one, are found.
There are no known public exploits for this vulnerability at the time of this report. However, it is important to patch your Jenkins installation to prevent potential exploitation.
No, there is no known workaround for this vulnerability. It is highly recommended to upgrade to the fixed version of the Script Security Plugin to mitigate the risk.
You can find more information about this vulnerability in the Jenkins Security Advisory https://www.jenkins.io/security/advisory/2017-08-07/#super-constructor-calls.
Related vulnerabilities
Recent vulnerabilities recorded for org.jenkins-ci.plugins:script-security.
