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.
{
"cna_assigner": "redhat",
"cwe_ids": [
"CWE-285"
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/8xxx/CVE-2024-8676.json",
"unresolved_ranges": [
{
"extracted_events": [
{
"range": [
{
"fixed": "0:1.28.11-7.rhaos4.15.gitc4c0556.el8"
},
{
"fixed": "0:1.29.11-3.rhaos4.16.git16d9bd6.el8"
},
{
"fixed": "416.94.202506251808-0"
},
{
"fixed": "417.94.202503241418-0"
},
{
"fixed": "0:1.31.5-5.rhaos4.18.git6dfa0a6.el8"
},
{
"fixed": "418.94.202504231329-0"
}
],
"source": "AFFECTED_FIELD",
"strategy": "InverseAffectedRanges"
}
]
}
]
}{
"extracted_events": [
{
"range": [
{
"introduced": "0"
},
{
"fixed": "1.29.11"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StandardRange"
},
{
"range": [
{
"introduced": "1.30.0"
},
{
"fixed": "1.30.8"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StandardRange"
},
{
"range": [
{
"introduced": "1.31.0"
},
{
"fixed": "1.31.3"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StandardRange"
}
]
}