Incorrect Default Permissions Affecting podman-docker package, versions <2:4.0.2-6.module+el8.6.0+14673+621cb8be


Severity

Recommended
high

Based on CentOS security rating

    Threat Intelligence

    EPSS
    0.13% (50th 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-2804611
  • published 1 Apr 2022
  • disclosed 30 Mar 2022

How to fix?

Upgrade Centos:8 podman-docker to version 2:4.0.2-6.module+el8.6.0+14673+621cb8be 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.

A flaw was found in buildah where containers were incorrectly started with non-empty default permissions. A bug was found in Moby (Docker Engine) where containers were incorrectly started with non-empty inheritable Linux process capabilities, enabling an attacker with access to programs with inheritable file capabilities to elevate those capabilities to the permitted set when execve(2) runs. This has the potential to impact confidentiality and integrity.

CVSS Scores

version 3.1
Expand this section

NVD

6.8 medium
  • Attack Vector (AV)
    Network
  • Attack Complexity (AC)
    High
  • Privileges Required (PR)
    Low
  • User Interaction (UI)
    None
  • Scope (S)
    Unchanged
  • Confidentiality (C)
    High
  • Integrity (I)
    High
  • Availability (A)
    None
Expand this section

Red Hat

4.8 medium
Expand this section

SUSE

5.9 medium