CVE Vulnerabilities

CVE-2018-10843

Incorrect Permission Assignment for Critical Resource

Published: Jul 02, 2018 | Modified: Oct 09, 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
9 HIGH
AV:N/AC:L/Au:S/C:C/I:C/A:C
RedHat/V2
RedHat/V3
8.5 IMPORTANT
CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
Ubuntu

source-to-image component of Openshift Container Platform before versions atomic-openshift 3.7.53, atomic-openshift 3.9.31 is vulnerable to a privilege escalation which allows the assemble script to run as the root user in a non-privileged container. An attacker can use this flaw to open network connections, and possibly other actions, on the host which are normally only available to a root user.

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
Openshift_container_platform Redhat * 3.7.53 (excluding)
Openshift_container_platform Redhat 3.9 (including) 3.9 (including)
Openshift_container_platform Redhat 3.9.31 (including) 3.9.31 (including)
Red Hat OpenShift Container Platform 3.9 RedHat atomic-openshift-0:3.9.31-1.git.0.ef9737b.el7 *
Red Hat OpenShift Container Platform 3.9 RedHat atomic-openshift-descheduler-0:3.9.13-1.git.267.bb59a3f.el7 *
Red Hat OpenShift Container Platform 3.9 RedHat atomic-openshift-dockerregistry-0:3.9.31-1.git.351.1bd46ed.el7 *
Red Hat OpenShift Container Platform 3.9 RedHat atomic-openshift-node-problem-detector-0:3.9.13-1.git.167.5d6b0d4.el7 *
Red Hat OpenShift Container Platform 3.9 RedHat atomic-openshift-web-console-0:3.9.31-1.git.246.bded6a4.el7 *
Red Hat OpenShift Container Platform 3.9 RedHat golang-github-prometheus-node_exporter-0:3.9.31-1.git.890.a55de06.el7 *
Red Hat OpenShift Container Platform 3.9 RedHat mysql-apb-role-0:1.1.11-1.el7 *
Red Hat OpenShift Container Platform 3.9 RedHat openshift-ansible-0:3.9.31-1.git.34.154617d.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