An information disclosure flaw was found in Buildah, when building containers using chroot isolation. Running processes in container builds (e.g. Dockerfile RUN commands) can access environment variables from parent and grandparent processes. When run in a container in a CI/CD environment, environment variables may include sensitive information that was shared with the container in order to be used only by Buildah itself (e.g. container registry credentials).
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 |
---|---|---|---|
Buildah | Buildah_project | * | 1.16.8 (excluding) |
Buildah | Buildah_project | 1.17.0 (including) | 1.17.2 (excluding) |
Buildah | Buildah_project | 1.19.0 (including) | 1.19.9 (excluding) |
Buildah | Buildah_project | 1.21.0 (including) | 1.21.3 (excluding) |
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.