CVE Vulnerabilities

CVE-2017-1000096

Incorrect Permission Assignment for Critical Resource

Published: Oct 05, 2017 | Modified: Oct 03, 2019
CVSS 3.x
8.8
HIGH
Source:
NVD
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS 2.x
6.5 MEDIUM
AV:N/AC:L/Au:S/C:P/I:P/A:P
RedHat/V2
RedHat/V3
8.8 IMPORTANT
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Ubuntu

Arbitrary code execution due to incomplete sandbox protection: Constructors, instance variable initializers, and instance initializers in Pipeline scripts were not subject to sandbox protection, and could therefore execute arbitrary code. This could be exploited e.g. by regular Jenkins users with the permission to configure Pipelines in Jenkins, or by trusted committers to repositories containing Jenkinsfiles.

Weakness

The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.

Affected Software

Name Vendor Start Version End Version
Pipeline:_groovy Jenkins * 2.36 (including)
Red Hat OpenShift Container Platform 3.6 RedHat atomic-openshift-0:3.6.173.0.21-1.git.0.f95b0e7.el7 *
Red Hat OpenShift Container Platform 3.6 RedHat fluentd-0:0.12.39-2.el7 *
Red Hat OpenShift Container Platform 3.6 RedHat jenkins-2-plugins-0:3.7.1502412812-1.el7 *
Red Hat OpenShift Container Platform 3.6 RedHat kibana-0:4.6.4-3.el7 *
Red Hat OpenShift Container Platform 3.6 RedHat rubygem-cool.io-0:1.5.1-1.el7 *
Red Hat OpenShift Container Platform 3.6 RedHat rubygem-excon-0:0.58.0-1.el7 *
Red Hat OpenShift Container Platform 3.6 RedHat rubygem-faraday-0:0.13.0-1.el7 *
Red Hat OpenShift Container Platform 3.6 RedHat rubygem-fluent-plugin-kubernetes_metadata_filter-0:0.29.0-1.el7 *
Red Hat OpenShift Container Platform 3.6 RedHat rubygem-fluent-plugin-viaq_data_model-0:0.0.5-1.el7 *
Red Hat OpenShift Container Platform 3.6 RedHat rubygem-i18n-0:0.8.6-1.el7 *
Red Hat OpenShift Container Platform 3.6 RedHat rubygem-systemd-journal-0:1.3.0-1.el7 *

Potential Mitigations

  • Run the code in a “jail” or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which files can be accessed in a particular directory or which commands can be executed by the software.
  • OS-level examples include the Unix chroot jail, AppArmor, and SELinux. In general, managed code may provide some protection. For example, java.io.FilePermission in the Java SecurityManager allows the software to specify restrictions on file operations.
  • This may not be a feasible solution, and it only limits the impact to the operating system; the rest of the application may still be subject to compromise.
  • Be careful to avoid CWE-243 and other weaknesses related to jails.

References