Sandbox bypass in Jenkins Script Security Plugin sandbox bypass

published 2017-10-04 9y ago modified 2026-06-17 4mo ago also GHSA-h7rx-r733-7x7r , EUVD-2022-4100

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

Script Security Plugin did not apply sandboxing restrictions to constructor invocations via positional arguments list, super constructor invocations, method references, and type coercion expressions. This could be used to invoke arbitrary constructors and methods, bypassing sandbox protection.

Patch / fix

fixed in 1

maven org.jenkins-ci.plugins:script-security 1.31

Is CVE-2017-1000107 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-2017-1000107 updated 2025-11-21 cvss 8.8

jenkins-plugin-workflow-cps: Multiple Groovy language features allowed Script Security Plugin sandbox bypass

Red Hat OpenShift Enterprise 3 jenkins-plugin-workflow-cps, jenkins-plugin-script-security
affected: no fix planned “Will not fix”

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.20% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-09).

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:script-security	<1.31	1.31

References

jenkins.io /security/advisory/2017-08-07/
vendor-advisory
nvd.nist.gov /vuln/detail/CVE-2017-1000107
advisory
jenkins.io /security/advisory/2017-08-07
web

Sources

Fencer Intel 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.