CVE-2024-8676

High

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.

SeverityHigh
CVSS7.4
Exploit probability—
ProductGithub.com/cri-o/cri-o
PublishedNov 26, 2024
First seenNov 26, 2024
Weakness typeCWE-285CWE-285

How to fix

Affected products

ProductAffected versionsFixed in
github.com/cri-o/cri-oGov < 1.29.11, 1.30.0 ≤ v < 1.30.8, 1.31.0 ≤ v < 1.31.31.29.11, 1.30.8, 1.31.3

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.

CVE-2024-8676 · Github.com/cri-o/cri-o · Dark Radar