Information disclosure in podman
podman
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/containers/podman/v2 Go |
|
|
| github.com/containers/libpod Go |
| No fix yet |
| github.com/containers/libpod/v2 Go |
|
podman
| Product | Affected | Fixed in |
|---|---|---|
| github.com/containers/podman/v2 Go |
|
|
| github.com/containers/libpod Go |
| No fix yet |
| github.com/containers/libpod/v2 Go |
|
|
An information disclosure vulnerability was found in containers/podman in versions before 2.0.5. When using the deprecated Varlink API or the Docker-compatible REST API, if multiple containers are created in a short duration, the environment variables from the first container will get leaked into subsequent containers. An attacker who has control over the subsequent containers could use this flaw to gain access to sensitive information stored in such variables.
From the CVE record · redhat
In podman before 2.0.5, creating multiple containers in a short time through the deprecated Varlink API or Docker-compatible REST API can leak environment variables from the first container into subsequent containers. An attacker who controls a subsequent container could access sensitive information in those variables.
Teams running podman before 2.0.5, github.com/containers/podman/v2 or github.com/containers/libpod/v2 before 2.0.5, or any version of github.com/containers/libpod should check.