dbcve.org
Pipeline\Application · Jenkins

CVE-2018-1000866

HIGH · 8.8 CVSS v3.0 Published 2018-12-10
Fix available
A fix is available. Upgrade to after 2.59 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 exists in Pipeline: Groovy Plugin 2.59 and earlier in groovy-sandbox/src/main/java/org/kohsuke/groovy/sandbox/SandboxTransformer.java, groovy-cps/lib/src/main/java/com/cloudbees/groovy/cps/SandboxCpsTransformer.java that allows attackers with Job/Configure permission, or unauthorized attackers with SCM commit privileges and corresponding pipelines based on Jenkinsfiles set up in Jenkins, 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

The Pipeline: Groovy Plugin 2.59 and earlier contains a sandbox bypass vulnerability in the SandboxTransformer and SandboxCpsTransformer components. Attackers with Job/Configure permission or unauthorized attackers with SCM commit privileges to Jenkinsfiles can circumvent Groovy sandbox restrictions and execute arbitrary code on the Jenkins master JVM.

MitigationUpgrade Pipeline: Groovy Plugin to version 2.60 or later to remediate this sandbox bypass vulnerability. Additionally, restrict Job/Configure permission and review SCM commit access to prevent unauthorized pipeline execution.

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
Pipeline\Application
Affected:<= 2.59
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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/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 Pipeline: Groovy Plugin version
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, locate Pipeline: Groovy Plugin in the list and check the Version column
    Affected if The installed version is 2.59 or earlier (the version number matches or is lower than the affected range)
  2. Confirm Pipeline plugin is present
    In the Jenkins plugin manager, verify that the Pipeline: Groovy Plugin is installed and enabled
    Affected if The plugin is installed and active in Jenkins
  3. Identify Pipeline jobs using Groovy sandbox
    Review Pipeline job configurations: go to each Pipeline job > Configure > look for 'Use Groovy Sandbox' checkbox in the Pipeline script section or check for 'groovy sandbox' keywords in Jenkinsfile content
    Affected if Jobs have the Groovy sandbox option enabled (the checkbox is checked) or Jenkinsfiles contain sandbox-related directives
  4. Check Job/Configure permission settings
    Navigate to Jenkins > Manage Jenkins > Manage and Assign Roles > check which users or groups have the Job/Configure permission, or review individual job security settings
    Affected if Users or groups beyond administrators have Job/Configure permission enabled
  5. Review SCM commit access to repositories with Jenkinsfiles
    Inspect the SCM configuration for repositories containing Jenkinsfiles and verify which users have commit/push privileges, particularly for unauthorized or external contributors
    Affected if Untrusted or unauthorized users have SCM commit access to Jenkinsfile-containing repositories

A user is affected if the Pipeline: Groovy Plugin version is 2.59 or lower AND Pipeline jobs with Groovy sandbox are in use, especially with overly permissive Job/Configure or SCM commit access.

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 2.59
Interim mitigation

Upgrade Pipeline: Groovy Plugin to version 2.60 or later to remediate this sandbox bypass vulnerability. Additionally, restrict Job/Configure permission and review SCM commit access to prevent unauthorized pipeline execution.

Fix this in Pipeline\ Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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