Cri O
Monthly
Container escape in CRI-O - the OCI runtime that underpins Red Hat OpenShift Container Platform 4 - is achievable when a workload-level actor can create or influence pod metadata that overwrites CRI-O's own reserved sandbox bookkeeping; the poisoned state is then reloaded as trusted after a CRI-O daemon restart, and a subsequent container recreate inside that sandbox can expose a host-side runtime-management resource to the container. Rated CVSS 3.1 7.8 (AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H), the flaw is not remotely reachable without cluster workload access, and the mandatory restart-then-recreate sequencing is the principal limiter on realistic exploitation. No public exploit code has been identified at time of analysis and the issue is not confirmed actively exploited (no CISA KEV listing); no EPSS score was supplied in the available intelligence.
Elevated-privilege container restoration in CRI-O 1.34 and later, including downstream Red Hat OpenShift Container Platform 4.17+, lets an authenticated Kubernetes user who can create a pod from a crafted checkpoint image bypass the destination pod's security context. The restored process keeps credentials, Linux capabilities, no_new_privs and seccomp state stored in the checkpoint instead of the destination configuration, allowing execution across the container security boundary. Exploitation requires non-default checkpoint/restore (CRIU) support to be enabled and RBAC permission to create pods from malicious checkpoints; no public exploit code is identified and no vendor-released fix is available at time of analysis, so the vendor CVSS 3.1 score of 8.8 overstates urgency given those prerequisites (our assessment raises attack complexity to High).
A path traversal (CWE-22) vulnerability in CRI-O's container checkpoint/restore feature allows a highly privileged, remote attacker to perform unintended operations on the host filesystem by supplying a malicious checkpoint archive during container restoration. Exploitation requires the non-default checkpoint/restore functionality to be enabled and the attacker to have high privileges (PR:H) to trigger restoration of untrusted content, resulting in a scope change from container to host with full confidentiality, integrity, and availability impact (CVSS 8.0). No public exploit identified at time of analysis. Affected products include Red Hat OpenShift Container Platform 4 as per CPE data.
A flaw was found in cri-o. Rated high severity (CVSS 8.1), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
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. Rated high severity (CVSS 7.1), this vulnerability is low attack complexity. Public exploit code available.
A vulnerability was found in CRI-O that causes memory or disk space exhaustion on the node for anyone with access to the Kube API. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available.
A flaw was found in cri-o, where containers were incorrectly started with non-empty default permissions. Rated medium severity (CVSS 5.3), this vulnerability is low attack complexity. No vendor patch available.
A flaw was found in CRI-O in the way it set kernel options for a pod. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
A flaw was found in cri-o, as a result of all pod-related processes being placed in the same memory cgroup. Rated medium severity (CVSS 5.0), this vulnerability is remotely exploitable. No vendor patch available.
Kubernetes CRI-O version prior to 1.9 contains a Privilege Context Switching Error (CWE-270) vulnerability in the handling of ambient capabilities that can result in containers running with elevated. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack complexity. This Improper Privilege Management vulnerability could allow attackers to escalate privileges to gain unauthorized elevated access.
Container escape in CRI-O - the OCI runtime that underpins Red Hat OpenShift Container Platform 4 - is achievable when a workload-level actor can create or influence pod metadata that overwrites CRI-O's own reserved sandbox bookkeeping; the poisoned state is then reloaded as trusted after a CRI-O daemon restart, and a subsequent container recreate inside that sandbox can expose a host-side runtime-management resource to the container. Rated CVSS 3.1 7.8 (AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H), the flaw is not remotely reachable without cluster workload access, and the mandatory restart-then-recreate sequencing is the principal limiter on realistic exploitation. No public exploit code has been identified at time of analysis and the issue is not confirmed actively exploited (no CISA KEV listing); no EPSS score was supplied in the available intelligence.
Elevated-privilege container restoration in CRI-O 1.34 and later, including downstream Red Hat OpenShift Container Platform 4.17+, lets an authenticated Kubernetes user who can create a pod from a crafted checkpoint image bypass the destination pod's security context. The restored process keeps credentials, Linux capabilities, no_new_privs and seccomp state stored in the checkpoint instead of the destination configuration, allowing execution across the container security boundary. Exploitation requires non-default checkpoint/restore (CRIU) support to be enabled and RBAC permission to create pods from malicious checkpoints; no public exploit code is identified and no vendor-released fix is available at time of analysis, so the vendor CVSS 3.1 score of 8.8 overstates urgency given those prerequisites (our assessment raises attack complexity to High).
A path traversal (CWE-22) vulnerability in CRI-O's container checkpoint/restore feature allows a highly privileged, remote attacker to perform unintended operations on the host filesystem by supplying a malicious checkpoint archive during container restoration. Exploitation requires the non-default checkpoint/restore functionality to be enabled and the attacker to have high privileges (PR:H) to trigger restoration of untrusted content, resulting in a scope change from container to host with full confidentiality, integrity, and availability impact (CVSS 8.0). No public exploit identified at time of analysis. Affected products include Red Hat OpenShift Container Platform 4 as per CPE data.
A flaw was found in cri-o. Rated high severity (CVSS 8.1), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
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. Rated high severity (CVSS 7.1), this vulnerability is low attack complexity. Public exploit code available.
A vulnerability was found in CRI-O that causes memory or disk space exhaustion on the node for anyone with access to the Kube API. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available.
A flaw was found in cri-o, where containers were incorrectly started with non-empty default permissions. Rated medium severity (CVSS 5.3), this vulnerability is low attack complexity. No vendor patch available.
A flaw was found in CRI-O in the way it set kernel options for a pod. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
A flaw was found in cri-o, as a result of all pod-related processes being placed in the same memory cgroup. Rated medium severity (CVSS 5.0), this vulnerability is remotely exploitable. No vendor patch available.
Kubernetes CRI-O version prior to 1.9 contains a Privilege Context Switching Error (CWE-270) vulnerability in the handling of ambient capabilities that can result in containers running with elevated. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack complexity. This Improper Privilege Management vulnerability could allow attackers to escalate privileges to gain unauthorized elevated access.