A vulnerability was found in CRI-O related to the container checkpoint and restore feature. When CRI-O is configured to restore containers from checkpoint archives, insufficient validation of restore metadata may allow a user with sufficient privileges to perform unintended operations on the host filesystem. Successful exploitation requires that container checkpoint and restore functionality is enabled, which is not the default configuration. An attacker must also be able to trigger restoration of a container from untrusted checkpoint content.
Until the relevant CRI-O/OpenShift security updates are available, this issue can be mitigated by implementing one or more of the following measures: 1. Do not enable container checkpoint and restore functionality unless it is explicitly required for your environment. 2. Restrict permissions to create workloads and to access node-level container runtime interfaces to trusted administrators only. 3. Do not restore containers from untrusted or unverified checkpoint sources.