Buildah processes using chroot isolation may leak environment values to intermediate processes
buildah
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/containers/buildah Go |
|
|
buildah
| Product | Affected | Fixed in |
|---|---|---|
| github.com/containers/buildah Go |
|
|
1.21.31.22.0An 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).
From the CVE record · redhat
Buildah builds using chroot isolation can expose environment variables from parent and grandparent processes to processes running inside the build, such as Dockerfile RUN commands. In CI/CD containers, those variables may contain sensitive information, including registry credentials intended only for Buildah. The disclosure requires a process running in a container build; the input does not specify authentication requirements or user interaction.
Teams using Go package github.com/containers/buildah should check installations in the listed affected ranges below 1.16.8, from 1.17.0 to below 1.17.2, from 1.18.0 to below 1.19.9, and from 1.20.0 to below 1.21.3, as well as versions below 1.22.0.