Skip to content
Fencer Intel
medium 6.5

CVE-2017-1000095 json

Unsafe methods in the default list of approved signatures in Jenkins Script Security Plugin

published 2017-10-04 9 y ago modified 2026-06-17 4 mo ago also GHSA-m68x-cc2f-gr5h , EUVD-2022-4503

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

Summary

The default whitelist included the following unsafe entries: DefaultGroovyMethods.putAt(Object, String, Object); DefaultGroovyMethods.getAt(Object, String). These allowed circumventing many of the access restrictions implemented in the script sandbox by using e.g. currentBuild['rawBuild'] rather than currentBuild.rawBuild. Additionally, the following entries allowed accessing private data that would not be accessible otherwise due to script security: groovy.json.JsonOutput.toJson(Closure); groovy.json.JsonOutput.toJson(Object).

Patch / fix

  • maven org.jenkins-ci.plugins:script-security 1.29.1
  • jenkins-plugin-script-security openshift 3.6 1.29-1.el7

red hat advisories RHEA-2017:1716

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-1000095 updated cvss 5.2

jenkins-plugin-script-security: Unsafe methods in the default whitelist (SECURITY-538)

  • Red Hat OpenShift Container Platform 3.5 jenkins-plugin-script-security
    affected: no fix planned “Will not fix”
  • Red Hat OpenShift Container Platform 3.6 jenkins-plugin-script-security 1.29-1.el7
    fixed: vendor fix RHEA-2017:1716
  • Red Hat OpenShift Container Platform 3.6 apb 0.1.2-1.el7, cockpit 147-1.el7, libuv 1.7.5-3.el7, scons 2.5.1-1.el7, fb303 0.9.1-14.el7, kibana 4.6.4-1.el7, +429 more
    not affected: vulnerable code not present

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

0.82% chance of exploitation in the next 30 days, higher than 57% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

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

Affected packages

ecosystem package affected fixed in
maven org.jenkins-ci.plugins:script-security
<1.29.1
1.29.1

Classification

Weakness
  • CWE-732 Incorrect Permission Assignment for Critical Resource

References

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.