dbcve.org
Script SecurityApplication · Jenkins

CVE-2019-10356

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 method pointer expressions 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 contains a sandbox bypass vulnerability in the handling of method pointer expressions, allowing attackers to execute arbitrary code within sandboxed Groovy scripts. The vulnerability exploits how the sandbox security layer processes method pointers to circumvent restrictions intended to prevent dangerous operations.

MitigationUpgrade Jenkins Script Security Plugin to version 1.62 or later. Review existing sandboxed scripts for indicators of compromise and implement additional approval workflows for untrusted pipeline 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
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 Script Security Plugin version
    Navigate to Jenkins UI: Manage Jenkins > Manage Plugins > Installed tab. Locate 'Script Security' plugin in the list and note the Version column. Alternatively, check the plugin's .jpi or .hpi file in $JENKINS_HOME/plugins/ for the version manifest.
    Affected if The installed version is 1.61 or earlier.
  2. Confirm sandboxed script usage
    Review Jenkins pipeline jobs and freestyle jobs that use the Script Security plugin. Check job configurations for 'Groovy Sandbox' checkbox enabled in build step script fields, or inspect Jenkinsfile definitions containing @Library or standard pipeline syntax.
    Affected if Sandboxed Groovy scripts are enabled and in use.
  3. Review script approval records
    Navigate to Manage Jenkins > In-process Script Approval. Examine the list of approved scripts and signatures. Look for any recently approved method pointer expressions or signatures that were not explicitly approved by administrators.
    Affected if Unrecognized or suspicious method pointer signatures appear in the approved list.
  4. Check OpenShift environment version (if applicable)
    If Jenkins runs on OpenShift, verify the OCP version via 'oc version' command or OpenShift web console under Help > About. This helps determine if the Jenkins instance operates in a known affected container platform version.
    Affected if OpenShift Container Platform version equals 3.11 or 4.1, and Jenkins with Script Security plugin <=1.61 is deployed.

You are affected if Jenkins Script Security Plugin version 1.61 or earlier is installed AND sandboxed Groovy scripts are actively used in your pipelines or jobs.

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. Review existing sandboxed scripts for indicators of compromise and implement additional approval workflows for untrusted pipeline scripts.

Fix this in Script Security Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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