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.
The product stores, transfers, or shares a resource that contains sensitive information, but it does not properly remove that information before the product makes the resource available to unauthorized actors.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Podman | Podman_project | * | 2.0.5 (excluding) |
| Red Hat Enterprise Linux 7 Extras | RedHat | podman-0:1.6.4-26.el7_9 | * |
| Red Hat Enterprise Linux 8 | RedHat | container-tools:rhel8-8030120210208205200.c127ee91 | * |
| Red Hat OpenShift Container Platform 4.6 | RedHat | podman-0:1.9.3-3.rhaos4.6.el8 | * |
| Libpod | Ubuntu | trusty | * |
| Libpod | Ubuntu | upstream | * |
Resources that may contain sensitive data include documents, packets, messages, databases, etc. While this data may be useful to an individual user or small set of users who share the resource, it may need to be removed before the resource can be shared outside of the trusted group. The process of removal is sometimes called cleansing or scrubbing. For example, a product for editing documents might not remove sensitive data such as reviewer comments or the local pathname where the document is stored. Or, a proxy might not remove an internal IP address from headers before making an outgoing request to an Internet site.