Vulnerability · Published Nov 26, 2024 · Assigned by redhat

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

High 7.4

In plain English

A high-severity security flaw in cri-o. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.8% (higher than 55% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)7.4High
Exploit odds (30 days)0.8%top 44.8% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official 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 packages & fixed versions

EcosystemPackageFixed inAdvisory
Gogithub.com/cri-o/cri-o1.29.11GHSA-7p9f-6x8j-gxxp
Gogithub.com/cri-o/cri-o1.30.8GHSA-7p9f-6x8j-gxxp
Gogithub.com/cri-o/cri-o1.31.3GHSA-7p9f-6x8j-gxxp
Gogithub.com/cri-o/cri-o1.29.11, 1.30.8, 1.31.3GO-2024-3292

Affected products (as reported)

Weakness: CWE-285 · Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

References