CVE-2017-1000095: Script security Unsafe Methods Vulnerability

MODERATE
Advisory Identifier: GHSA-m68x-cc2f-gr5h
CVSS 6.5
CWE-732
Published
Advisory Summary

CVE-2017-1000095 is a MODERATE (CVSS 6.5) unsafe methods vulnerability (CWE-732: Incorrect Permission Assignment for Critical Resource) affecting Script security libraries in the Maven ecosystem. The issue involves unsafe methods in the default list of approved signatures in jenkins script security plugin. Remediation is available by upgrading affected packages to version 1.29.1.

CVE-2017-1000095 at a Glance

CVE Identifier CVE-2017-1000095
GHSA Identifier GHSA-m68x-cc2f-gr5h
Severity MODERATE
CVSS v3.1 Base Score 6.5
CWE Classification CWE-732: Incorrect Permission Assignment for Critical Resource
Affected Product Script security
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 6.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2017-1000095

To remediate this vulnerability, upgrade all affected Script security dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

org.jenkins-ci.plugins:script-security fixed: 1.29.1
<dependency>
    <groupId>org.jenkins-ci.plugins</groupId>
    <artifactId>script-security</artifactId>
    <version>1.29.1</version>
</dependency>
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

mvn dependency:tree -Dincludes=org.jenkins-ci.plugins

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2017-1000095, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree -Dincludes=org.jenkins-ci.plugins

Analyze the terminal output to locate any version of Script security in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.29.1), your application is affected.

Note: The mvn dependency:tree -Dincludes=org.jenkins-ci.plugins command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-732: Incorrect Permission Assignment for Critical Resource, where the product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors. In Script security, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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).

CVE-2017-1000095 Affected Script security Versions

1 component(s)
Fixed Versions:
1.29.1
Product / Package Ecosystem Affected Versions Fixed Version
org.jenkins-ci.plugins:script-security
Maven
< 1.29.1
1.29.1

References

Frequently Asked Questions

What is CVE-2017-1000095?
CVE-2017-1000095 is a security vulnerability in Script security involving Unsafe methods in the default list of approved signatures in Jenkins Script Security Plugin under CWE-732: Incorrect Permission Assignment for Critical Resource.
Which Script security versions are affected?
Affected versions include releases prior to 1.29.1 across affected packages: org.jenkins-ci.plugins:script-security.
What version fixes CVE-2017-1000095?
Upgrading to 1.29.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is script-security affected?
Yes, org.jenkins-ci.plugins:script-security is affected in releases prior to 1.29.1. Upgrade your dependency to 1.29.1 or later.
What is the CVSS score of CVE-2017-1000095?
CVE-2017-1000095 has a CVSS v3.1 base score of 6.5 (MODERATE) with vector string CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2017-1000095?
CVE-2017-1000095 is classified under CWE-732: Incorrect Permission Assignment for Critical Resource (The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.).
How can I check Maven dependencies for CVE-2017-1000095?
Run the dependency tree command: 'mvn dependency:tree -Dincludes=org.jenkins-ci.plugins'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-m68x-cc2f-gr5h",
  "modified" : "2024-01-30T22:46:07Z",
  "published" : "2022-05-13T01:40:54Z",
  "aliases" : [ "CVE-2017-1000095" ],
  "summary" : "Unsafe methods in the default list of approved signatures in Jenkins Script Security Plugin",
  "details" : "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).",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.jenkins-ci.plugins:script-security"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.29.1"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 1.29"
    }
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2017-1000095"
  }, {
    "type" : "WEB",
    "url" : "https://jenkins.io/security/advisory/2017-07-10"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-732" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2024-01-30T22:46:07Z",
    "nvd_published_at" : "2017-10-05T01:29:00Z"
  }
}