Kurz gesagt
- CVE-2024-8676 ist eine Schwachstelle (HOCH (CVSS 7.4)) in github.com/cri-o/cri-o.
- Wahrscheinlichkeit einer Ausnutzung in den nächsten 30 Tagen (EPSS): 0.75%, höher als bei 55.0% aller Schwachstellen.
- Abhilfe: auf 1.30.8, 1.31.3, 1.29.11 oder neuer aktualisieren.
| Package | Affected versions | Patched versions |
|---|
| github.com/cri-o/cri-o Go | ≥ 1.30.0, < 1.30.8≥ 1.31.0, < 1.31.3< 1.29.11
| 1.30.81.31.31.29.11
|
Description
Impact
Patches
1.31.1, 1.30.6, 1.29.8
Workarounds
set enable_criu_support = false
References
Are there any links users can visit to find out more?
NVD 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.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free