Improper Authorization Affecting container-tools:rhel8/podman-gvproxy package, versions *


Severity

Recommended
medium

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.04% (11th 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-RHEL8-CONTAINERTOOLS-8441332
  • published27 Nov 2024
  • disclosed26 Nov 2024

Introduced: 26 Nov 2024

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

How to fix?

There is no fixed version for RHEL:8 container-tools:rhel8/podman-gvproxy.

NVD Description

Note: Versions mentioned in the description apply only to the upstream container-tools:rhel8/podman-gvproxy package and not the container-tools:rhel8/podman-gvproxy package as distributed by RHEL. See How to fix? for RHEL:8 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