Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 16 May 2022.
Script SecurityApplication · Jenkins

CVE-2019-1003029

CRITICAL · 9.9 CVSS v3.1 Published 2019-03-08
Fix available
A fix is available. Upgrade to after 1.53 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit 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 exists in Jenkins Script Security Plugin 1.53 and earlier in src/main/java/org/jenkinsci/plugins/scriptsecurity/sandbox/groovy/GroovySandbox.java, src/main/java/org/jenkinsci/plugins/scriptsecurity/sandbox/groovy/SecureGroovyScript.java that allows attackers with Overall/Read permission to execute arbitrary code on the Jenkins master 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

A sandbox bypass vulnerability in Jenkins Script Security Plugin 1.53 and earlier in GroovySandbox.java and SecureGroovyScript.java allows attackers with Overall/Read permission to execute arbitrary code on the Jenkins master JVM by circumventing script security restrictions.

MitigationUpgrade Jenkins Script Security Plugin to version 1.54 or later to resolve the sandbox bypass. Verify existing approved scripts continue functioning properly after the upgrade.

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.53
Openshift Container PlatformApplication
Affected:= 3.11

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. Verify Script Security Plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and look for 'Script Security' in the list, or check the $JENKINS_HOME/plugins directory for the script-security folder
    Affected if The plugin is present in the plugin list or filesystem
  2. Determine the installed version of Script Security Plugin
    In Jenkins > Manage Jenkins > Manage Plugins > Installed tab, find Script Security and note the Version column; alternatively, check the version file in $JENKINS_HOME/plugins/script-security/META-INF/MANIFEST.MF
    Affected if The version number is 1.53 or earlier
  3. Confirm Groovy sandbox is in use
    Look for Pipeline jobs, Jenkinsfile executions, or Groovy scripts that use the sandboxed execution mode; check job configurations for 'Use Groovy Sandbox' checkbox enabled under the Pipeline Script section
    Affected if Groovy sandbox (GroovySandbox.java or SecureGroovyScript.java) is being used to execute scripts
  4. Check for Overall/Read permission assignments
    Navigate to Jenkins > Manage Jenkins > Manage Users and review user accounts, then check Jenkins > Manage Jenkins > Configure Global Security > Authorization to see which users or groups have Overall/Read permission
    Affected if Any user account or group has Overall/Read permission granted (especially untrusted or shared accounts)
  5. Verify if untrusted users can access Jenkins
    Review the authorization matrix in Jenkins > Manage Jenkins > Configure Global Security to identify which users or groups have Overall/Read access, particularly looking for users beyond trusted administrators
    Affected if Untrusted or unauthorized users have Overall/Read access to the Jenkins instance

You are affected if Jenkins Script Security Plugin version 1.53 or earlier is installed, Groovy sandbox execution is enabled, and untrusted users have Overall/Read permission to access Jenkins.

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.53
Interim mitigation

Upgrade Jenkins Script Security Plugin to version 1.54 or later to resolve the sandbox bypass. Verify existing approved scripts continue functioning properly after the upgrade.

Recommended fix High confidence

Script Security Plugin version 1.54 or later

  1. Log in to Jenkins as an administrator with overall admin permission
  2. Navigate to 'Manage Jenkins' > 'Manage Plugins'
  3. Click on the 'Installed' tab to view installed plugins
  4. Locate the 'Script Security' plugin in the list
  5. Verify the current installed version is 1.53 or earlier
  6. If an update is available, select the Script Security plugin and click 'Update'
  7. Alternatively, if no update is shown, download the fixed version from the Jenkins plugin repository manually
  8. Restart Jenkins after the plugin update to ensure the new version is loaded
Caveat Review pipeline scripts and Groovy code for compatibility after upgrade, as sandbox behavior may change

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

Fix this in Script Security Exploited in the wild — priority engagement
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
14.0 hours of engineering $2,400
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-1003029 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-1003029 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