dbcve.org
Script SecurityApplication · Jenkins

CVE-2020-2279

CRITICAL · 9.9 CVSS v3.1 Published 2020-09-23
Fix available
A fix is available. Upgrade to after 1.74 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
A sandbox bypass vulnerability in Jenkins Script Security Plugin 1.74 and earlier allows attackers with permission to define sandboxed scripts to provide crafted return values or script binding content that can result in arbitrary code execution on the Jenkins controller JVM.

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 confidence

This is a sandbox bypass vulnerability in Jenkins Script Security Plugin versions 1.74 and earlier. Attackers with permission to define sandboxed Groovy scripts can provide crafted return values or script binding content that escapes the sandbox, allowing arbitrary code execution on the Jenkins controller JVM.

MitigationUpgrade Jenkins Script Security Plugin to version 1.75 or later. Until the upgrade is applied, restrict permissions for users who can define sandboxed scripts and audit existing scripts for malicious content.

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
Affected:<= 1.74

CVSS 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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the Script Security Plugin
    In Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab and search for 'Script Security' plugin, or check the JENKINS_HOME/plugins directory for the script-security folder
    Affected if The plugin is not installed (not affected) or installed version is 1.74 or earlier (affected)
  2. Determine the installed version
    In the plugin manager, note the version number shown for the Script Security plugin, or check the MANIFEST.MF file inside JENKINS_HOME/plugins/script-security/WEB-INF/lib/script-security*.jar
    Affected if Version is 1.74 or lower (affected)
  3. Check if sandboxed Groovy script execution is permitted
    Go to Manage Jenkins > In-process Script Approval and review whether any sandboxed scripts have been approved or if users have permission to submit them. Also check job configurations that use Groovy scripts with sandbox enabled.
    Affected if Users with Script permission can define sandboxed Groovy scripts (the exploit requires this permission)
  4. Review user permissions
    Go to Manage Jenkins > Manage Users and check which users or groups have the 'Script' or 'Script Security' permission. Also review Matrix Authorization Strategy if enabled.
    Affected if Any untrusted users or groups have permission to define sandboxed scripts (they could exploit this vulnerability)

You are affected if Script Security Plugin version 1.74 or earlier is installed AND users with Script permission can define sandboxed Groovy scripts in your Jenkins environment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 1.74
Interim mitigation

Upgrade Jenkins Script Security Plugin to version 1.75 or later. Until the upgrade is applied, restrict permissions for users who can define sandboxed scripts and audit existing scripts for malicious content.

Recommended fix High confidence

Script Security Plugin version 1.75 or later

  1. 1. Navigate to Jenkins Dashboard > Manage Jenkins > Manage Plugins
  2. 2. Go to the 'Installed' tab
  3. 3. Find 'Script Security' plugin in the list
  4. 4. If automatic updates are enabled, check for updates and install version 1.75 or later
  5. 5. Alternatively, download the latest version from the Jenkins plugin repository
  6. 6. Restart Jenkins after plugin installation to apply changes
  7. 7. Verify the plugin version shows 1.75 or later in the installed plugins list

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Script Security Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-2279 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-2279 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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