CVE-2024-8676: Cri-o: checkpoint restore can be triggered from different namespaces

Severity: high (CVSS 7.4 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.8% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2024-11-26 · updated 2026-10-13
Weakness: CWE-285

Description

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.

Affected products

Red Hat OpenShift Container Platform 4.18: all versions — fixed in 0:1.31.5-5.rhaos4.18.git6dfa0a6.el8, 418.94.202504231329-0
Red Hat Enterprise Linux 8: all versions
Red Hat Enterprise Linux 9: all versions
Red Hat OpenShift Container Platform 4.15: all versions — fixed in 0:1.28.11-7.rhaos4.15.gitc4c0556.el8
Red Hat OpenShift Container Platform 4.16: all versions — fixed in 0:1.29.11-3.rhaos4.16.git16d9bd6.el8, 416.94.202506251808-0
Red Hat OpenShift Container Platform 4.17: all versions — fixed in 417.94.202503241418-0

How to fix

Upgrade to a fixed version: Red Hat OpenShift Container Platform 4.18 0:1.31.5-5.rhaos4.18.git6dfa0a6.el8, 418.94.202504231329-0; Red Hat OpenShift Container Platform 4.15 0:1.28.11-7.rhaos4.15.gitc4c0556.el8; Red Hat OpenShift Container Platform 4.16 0:1.29.11-3.rhaos4.16.git16d9bd6.el8, 416.94.202506251808-0; Red Hat OpenShift Container Platform 4.17 417.94.202503241418-0. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2024-8676 or the next vulnerability affects your stack