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).
The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Storage | Storage_project | * | 1.28.1 (excluding) |
| Golang-github-containers-storage | Ubuntu | groovy | * |
| Golang-github-containers-storage | Ubuntu | hirsute | * |
| Golang-github-containers-storage | Ubuntu | impish | * |
| Golang-github-containers-storage | Ubuntu | kinetic | * |
| Golang-github-containers-storage | Ubuntu | lunar | * |
| Golang-github-containers-storage | Ubuntu | mantic | * |
| Golang-github-containers-storage | Ubuntu | trusty | * |
| Red Hat Enterprise Linux 8 | RedHat | container-tools:3.0-8050020220104131412.e34216c9 | * |
| Red Hat Enterprise Linux 8 | RedHat | container-tools:rhel8-8050020210921082437.faa19cc5 | * |
| Red Hat Enterprise Linux 9 | RedHat | podman-2:4.2.0-3.el9 | * |
| Red Hat Enterprise Linux 9 | RedHat | skopeo-2:1.9.2-1.el9 | * |
| Red Hat Enterprise Linux 9 | RedHat | buildah-1:1.27.0-2.el9 | * |
| Red Hat OpenShift Container Platform 4.7 | RedHat | cri-o-0:1.20.2-6.rhaos4.7.gitf1d5201.el8 | * |
| Red Hat OpenShift Container Platform 4.7 | RedHat | openshift-0:4.7.0-202104090228.p0.git.97111.77863f8.el8 | * |
| Red Hat OpenShift Container Platform 4.8 | RedHat | openshift4/ose-docker-builder:v4.8.0-202107152024.p0.git.70b7b95.assembly.stream | * |
Locking is a type of synchronization behavior that ensures that multiple independently-operating processes or threads do not interfere with each other when accessing the same resource. All processes/threads are expected to follow the same steps for locking. If these steps are not followed precisely - or if no locking is done at all - then another process/thread could modify the shared resource in a way that is not visible or predictable to the original process. This can lead to data or memory corruption, denial of service, etc.