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.

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

授权机制不恰当

CRI-O 授权问题漏洞

CRI-O是CRI-O开源的一款用于Kubernetes系统的轻量级容器运行时环境。 CRI-O存在授权问题漏洞，该漏洞源于允许攻击者诱骗CRI-O恢复无权访问主机挂载的pod。

N/A

N/A