Information Exposure Affecting podman-docker package, versions <3:4.6.1-8.module+el8.9.0+21243+a586538b


Severity

Recommended
0.0
high
0
10

Based on CentOS security rating

    Threat Intelligence

    EPSS
    5.06% (94th 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 ID SNYK-CENTOS8-PODMANDOCKER-6240695
  • published 9 Feb 2024
  • disclosed 31 Jan 2024

How to fix?

Upgrade Centos:8 podman-docker to version 3:4.6.1-8.module+el8.9.0+21243+a586538b or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream podman-docker package and not the podman-docker package as distributed by Centos. See How to fix? for Centos:8 relevant fixed versions and status.

runc is a CLI tool for spawning and running containers on Linux according to the OCI specification. In runc 1.1.11 and earlier, due to an internal file descriptor leak, an attacker could cause a newly-spawned container process (from runc exec) to have a working directory in the host filesystem namespace, allowing for a container escape by giving access to the host filesystem ("attack 2"). The same attack could be used by a malicious image to allow a container process to gain access to the host filesystem through runc run ("attack 1"). Variants of attacks 1 and 2 could be also be used to overwrite semi-arbitrary host binaries, allowing for complete container escapes ("attack 3a" and "attack 3b"). runc 1.1.12 includes patches for this issue.

CVSS Scores

version 3.1
Expand this section

NVD

8.6 high
  • Attack Vector (AV)
    Local
  • Attack Complexity (AC)
    Low
  • Privileges Required (PR)
    None
  • User Interaction (UI)
    Required
  • Scope (S)
    Changed
  • Confidentiality (C)
    High
  • Integrity (I)
    High
  • Availability (A)
    High
Expand this section

Red Hat

8.6 high
Expand this section

SUSE

8.6 high