CVE-2024-8676
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.
INFO
Published Date :
Nov. 26, 2024, 8:15 p.m.
Last Modified :
April 3, 2025, 11:15 a.m.
Source :
[email protected]
Remotely Exploitable :
Yes !
Impact Score :
5.2
Exploitability Score :
2.2
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2024-8676.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2024-8676 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2024-8676 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by [email protected]
Apr. 03, 2025
Action Type Old Value New Value Added Reference https://access.redhat.com/errata/RHSA-2025:3297 -
CVE Modified by [email protected]
Mar. 04, 2025
Action Type Old Value New Value Added Reference https://access.redhat.com/errata/RHSA-2025:1908 -
CVE Modified by [email protected]
Jan. 29, 2025
Action Type Old Value New Value Added Reference https://access.redhat.com/errata/RHSA-2025:0648 -
CVE Modified by [email protected]
Dec. 17, 2024
Action Type Old Value New Value Added Reference https://access.redhat.com/errata/RHBA-2024:10826 -
New CVE Received by [email protected]
Nov. 26, 2024
Action Type Old Value New Value Added 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. Added CVSS V3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N Added CWE CWE-285 Added Reference https://access.redhat.com/security/cve/CVE-2024-8676 Added Reference https://bugzilla.redhat.com/show_bug.cgi?id=2313842
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2024-8676 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2024-8676
weaknesses.