CVE-2024-8676
Cri-o: checkpoint restore can be triggered from different namespaces
We use these services and cookies to improve your user experience. You may opt out if you wish, however, this may limit some features on this site.
Please see our statement on Data Privacy.
Cri-o: checkpoint restore can be triggered from different namespaces
A vulnerability was found in CRI-O, where it can be requested to take a checkpoint archive of a container and later be asked to restore it. When it does that restoration, it attempts to restore the mounts from the restore archive instead of the pod request. As a result, the validations run on the pod spec, verifying that the pod has access to the mounts it specifies are not applicable to a restored container. This flaw allows a malicious user to trick CRI-O into restoring a pod that doesn't have access to host mounts. The user needs access to the kubelet or cri-o socket to call the restore endpoint and trigger the restore.
Reserved 2024-09-10 | Published 2024-11-26 | Updated 2024-12-03 | Assigner redhat| 2024-09-20: | Reported to Red Hat. |
| 2024-11-26: | Made public. |
access.redhat.com/security/cve/CVE-2024-8676
bugzilla.redhat.com/show_bug.cgi?id=2313842 (RHBZ#2313842)
Support options
