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.
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
| 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.el7 | * |
| 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 | * |
Access control involves the use of several protection mechanisms such as:
When any mechanism is not applied or otherwise fails, attackers can compromise the security of the product by gaining privileges, reading sensitive information, executing commands, evading detection, etc. There are two distinct behaviors that can introduce access control weaknesses: