CVE Vulnerabilities

CVE-2022-2995

Incorrect Permission Assignment for Critical Resource

Published: Sep 19, 2022 | Modified: Sep 21, 2022
CVSS 3.x
7.1
HIGH
Source:
NVD
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
CVSS 2.x
RedHat/V2
RedHat/V3
3.6 LOW
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N
Ubuntu
MEDIUM

Incorrect handling of the supplementary groups in the CRI-O container engine might lead to sensitive information disclosure or possible data modification if an attacker has direct access to the affected container where supplementary groups are used to set access permissions and is able to execute a binary code in that container.

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
Cri-o Kubernetes 1.25.0 (including) 1.25.0 (including)
Red Hat OpenShift Container Platform 4.10 RedHat cri-o-0:1.23.5-11.rhaos4.10.gitfc32aac.el8 *
Red Hat OpenShift Container Platform 4.11 RedHat cri-o-0:1.24.5-5.rhaos4.11.git8bf967b.el8 *
Red Hat OpenShift Container Platform 4.12 RedHat cri-o-0:1.25.1-5.rhaos4.12.git6005903.el8 *

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