<p>Upgrade <code>Centos:8</code> <code>podman-docker</code> to version 0:3.3.1-9.module+el8.5.0+12697+018f24d7 or higher.</p>

Improper Locking Affecting podman-docker package, versions <0:3.3.1-9.module+el8.5.0+12697+018f24d7

Threat Intelligence

0.52% (78^th 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-1957173
published 26 Jul 2021
disclosed 1 Apr 2021

Report a new vulnerability Found a mistake?

Introduced: 1 Apr 2021

CVE-2021-20291 Open this link in a new tab CWE-667 Open this link in a new tab

How to fix?

Upgrade Centos:8 podman-docker to version 0:3.3.1-9.module+el8.5.0+12697+018f24d7 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 deadlock vulnerability was found in 'github.com/containers/storage' in versions before 1.28.1. When a container image is processed, each layer is unpacked using tar. If one of those layers is not a valid tar archive this causes an error leading to an unexpected situation where the code indefinitely waits for the tar unpacked stream, which never finishes. An attacker could use this vulnerability to craft a malicious image, which when downloaded and stored by an application using containers/storage, would then cause a deadlock leading to a Denial of Service (DoS).

References

CVSS Scores

version 3.1

Attack Vector (AV)

Network
Attack Complexity (AC)

Low
Privileges Required (PR)

None
User Interaction (UI)

Required

Scope (S)

Unchanged

Confidentiality (C)

None
Integrity (I)

None
Availability (A)

High

Improper Locking Affecting podman-docker package, versions <0:3.3.1-9.module+el8.5.0+12697+018f24d7

Severity

Based on CentOS security rating