Improper Authorization Affecting cri-o package, versions <0:1.29.11-3.rhaos4.16.git16d9bd6.el9


Severity

Recommended
medium

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.05% (18th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL9-CRIO-8690252
  • published8 Feb 2025
  • disclosed26 Nov 2024

Introduced: 26 Nov 2024

CVE-2024-8676  (opens in a new tab)
CWE-285  (opens in a new tab)

How to fix?

Upgrade RHEL:9 cri-o to version 0:1.29.11-3.rhaos4.16.git16d9bd6.el9 or higher.
This issue was patched in RHBA-2024:10826.

NVD Description

Note: Versions mentioned in the description apply only to the upstream cri-o package and not the cri-o package as distributed by RHEL. See How to fix? for RHEL:9 relevant fixed versions and status.

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.

CVSS Scores

version 3.1