dbcve.org
Script SecurityApplication · Jenkins

CVE-2019-10355

HIGH · 8.8 CVSS v3.1 Published 2019-07-31
Fix available
A fix is available. Upgrade to after 1.61 or later.
See remediation →
94/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.61 and earlier related to the handling of type casts allowed attackers to execute arbitrary code in sandboxed scripts.

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

Jenkins Script Security Plugin versions 1.61 and earlier contain a sandbox bypass vulnerability in how type casts are handled. Attackers who can submit sandboxed scripts (e.g., through pipeline builds) can circumvent the sandbox restrictions and execute arbitrary code on the Jenkins controller or agent nodes.

MitigationUpgrade Jenkins Script Security Plugin to version 1.62 or later. Before deployment, audit existing pipeline scripts and jobs for any malicious submissions, and test the updated plugin in a staging environment to verify sandbox enforcement functions correctly.

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

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
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 checks

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

  1. Identify Jenkins Script Security Plugin version
    Navigate to Manage Jenkins > Manage Plugins > Installed tab, or check the plugin's manifest file (jenkins/plugins/script-security/META-INF/MANIFEST.MF) to find the installed version number
    Affected if The installed version is 1.61 or earlier
  2. Verify the plugin is loaded and active
    Check the Jenkins script security system configuration at Manage Jenkins > Configure Global Security > Script Security section, or query the Jenkins API endpoint /pluginManager/plugin/script-security to confirm the plugin status
    Affected if The Script Security Plugin is enabled and the version is 1.61 or earlier
  3. Confirm sandboxed script execution is permitted
    Review Job configurations for Pipeline or other job types that allow users to submit scripts. Check if the 'Use Groovy Sandbox' option is enabled in Pipeline job settings, or review authorization matrices for who can configure or run scripts
    Affected if Users or automated processes can submit or run sandboxed Groovy scripts through Pipelines or similar features
  4. Check for recent or untrusted pipeline job submissions
    Audit recent build history and pipeline scripts in jobs where users can provide custom Groovy code. Look for jobs using the sandbox that were created or modified by users who are not Jenkins administrators
    Affected if There are pipeline jobs using the sandbox that accept user-supplied scripts from non-admin users

You are affected if Jenkins Script Security Plugin version 1.61 or earlier is installed and your Jenkins environment permits users to submit or run sandboxed scripts through features like Pipelines.

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.

From vendor data
Upgrade available Upgrade to a release after 1.61
Interim mitigation

Upgrade Jenkins Script Security Plugin to version 1.62 or later. Before deployment, audit existing pipeline scripts and jobs for any malicious submissions, and test the updated plugin in a staging environment to verify sandbox enforcement functions correctly.

Fix this in Script Security Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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