Skip to content
Fencer Vulns
high 8.8

CVE-2018-1000866 json

Jenkins Script Security and Pipeline Groovy Plugins Sandbox Bypass

published 2018-12-10 7 y ago modified 2026-06-17 4 mo ago also GHSA-gqhm-4h93-rrhg , EUVD-2022-3993

cvss
8.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.6%
EPSS 1.6% chance of exploitation in 30 days, percentile 76%
public exploits
0
none known

Summary

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

Patch / fix

  • maven org.jenkins-ci.plugins.workflow:workflow-cps 2.60
  • maven org.jenkins-ci.plugins:script-security 1.48
  • haproxy openshift 3.11 1.8.17-3.el7
  • jenkins openshift 3.11 2.150.2.1549032159-1.el7
  • haproxy18 openshift 3.11 1.8.17-3.el7
  • prometheus openshift 3.11 3.11.82-1.git.5027.9d24833.el7
  • atomic-openshift openshift 3.11 3.11.82-1.git.0.08bc31b.el7
  • jenkins-2-plugins openshift 3.11 3.11.1549642489-1.el7
  • openshift-ansible openshift 3.11 3.11.82-3.git.0.9718d0a.el7
  • atomic-openshift-pod openshift 3.11 3.11.82-1.git.0.08bc31b.el7

red hat advisories RHBA-2019:0326

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-1000866 updated cvss 8.8

jenkins-plugin-script-security: Sandbox Bypass in finalize methods

  • Red Hat OpenShift Container Platform 3.2 jenkins-plugin-workflow-cps, jenkins-plugin-script-security Red Hat OpenShift Container Platform 3.3 jenkins-plugin-workflow-cps, jenkins-plugin-script-security Red Hat OpenShift Container Platform 3.4 jenkins-plugin-workflow-cps, jenkins-plugin-script-security Red Hat OpenShift Container Platform 3.5 jenkins-plugin-workflow-cps, jenkins-plugin-script-security Red Hat OpenShift Container Platform 3.6 jenkins-plugin-workflow-cps, jenkins-plugin-script-security Red Hat OpenShift Container Platform 3.7 jenkins-plugin-workflow-cps, jenkins-plugin-script-security
    +4 more products
    Red Hat OpenShift Container Platform 3.9 jenkins-plugin-workflow-cps, jenkins-plugin-script-security Red Hat OpenShift Container Platform 3.10 jenkins-plugin-workflow-cps, jenkins-plugin-script-security Red Hat OpenShift Container Platform 3.11 jenkins-plugin-script-security Red Hat OpenShift Enterprise 3.1 jenkins-plugin-workflow-cps, jenkins-plugin-script-security
    affected: workaround, no fix available “Do not run untrusted jenkins pipeline scripts.”
  • Red Hat OpenShift Container Platform 3.11 haproxy 1.8.17-3.el7, haproxy18 1.8.17-3.el7, jenkins 2.150.2.1549032159-1.el7, jenkins-2-plugins 3.11.1549642489-1.el7, prometheus 3.11.82-1.git.5027.9d24833.el7, atomic-openshift 3.11.82-1.git.0.08bc31b.el7, +33 more
    fixed: vendor fix “Do not run untrusted jenkins pipeline scripts.” RHBA-2019:0326

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.64% chance of exploitation in the next 30 days, higher than 76% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.0 8.8 CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 6.5 AV:N/AC:L/Au:S/C:P/I:P/A:P
GitHub 3.0 8.8 CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven org.jenkins-ci.plugins.workflow:workflow-cps
<2.60
2.60
maven org.jenkins-ci.plugins:script-security
<1.48
1.48

Classification

Weakness
  • CWE-269 Improper Privilege Management

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.