Script SecurityApplication · Jenkins
CVE-2020-2134
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSandbox protection in Jenkins Script Security Plugin 1.70 and earlier could be circumvented through crafted constructor calls and crafted constructor bodies.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Jenkins Script Security Plugin versions 1.70 and earlier had a sandbox bypass vulnerability where specially crafted constructor calls and constructor bodies could circumvent sandbox protections that normally restrict dangerous operations in Groovy scripts.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Script SecurityApplication
<= 1.70CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Script Security Plugin is installedGo to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or check the $JENKINS_HOME/plugins directory for the script-security folderAffected if The plugin is not installed, then the vulnerability does not apply (though other security concerns may exist)
-
Determine installed version of Script Security PluginIn Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed tab and locate 'Script Security Plugin' to read the version number. Alternatively, check the version file in $JENKINS_HOME/plugins/script-security/META-INF/MANIFEST.MFAffected if Version is 1.70 or earlier
-
Check if Groovy scripting is in useReview Jenkins jobs, pipelines, or shared libraries that use the Groovy language. Look for scripts using the 'script' step, inline Groovy code, or calls to Script Security-approved methodsAffected if Groovy scripts with constructor calls or constructor bodies are being executed in Jenkins
-
Review sandboxed scripts for dangerous constructor patternsExamine any Groovy scripts running in sandbox mode for constructor calls like 'new SomeClass()' or constructor bodies that may attempt to bypass sandbox restrictionsAffected if Scripts contain constructor-based patterns that could exploit the bypass
-
Check Jenkins logs for sandbox violation attemptsReview Jenkins logs (var/log/jenkins/jenkins.log) for any 'Permission denied' messages or sandbox-related security events that may indicate exploitation attemptsAffected if Logs show successful sandbox bypasses or unusual constructor-based access patterns
A user is affected if the Script Security Plugin version is 1.70 or earlier AND Groovy scripts using constructor calls are being executed in the Jenkins environment.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade Jenkins Script Security Plugin to version 1.71 or later to receive the sandbox protection fix.
Fix this in Script Security
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-2134 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-2134 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data