CVE-2021-3602: Infoleak

Published Jun 8, 2021
·
Updated

Impact When running processes using "chroot" isolation, the process being run can examine the environment variables of its immediate parent and grandparent processes (CVE-2021-3602). This isolation type is often used when running buildah in unprivileged containers, and it is often used to do so in CI/CD environments. If sensitive information is exposed to the original buildah process through its environment, that information will unintentionally be shared with child processes which it starts as part of handling RUN instructions or during buildah run. The commands that buildah is instructed to run can read that information if they choose to.

Patches Users should upgrade packages, or images which contain packages, to include version 1.21.3 or later.

Workarounds As a workaround, invoking buildah in a container under env -i to have it started with a reinitialized environment should prevent the leakage.

For more information If you have any questions or comments about this advisory: Open an issue in buildah Email us at the buildah general mailing list, or the podman security mailing list if it's sensitive.

Other sources

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).

Launchpad

An information disclosure vulnerability was found in buildah, when using buildah bud with chroot isolation. Dockerfile RUN commands executed during rootless buildah bud execution can read environment variables from the host, which may include sensitive information, such as container registry credentials.

Red Hat

Affected Software

16 affected componentsFixes available
go/github.com/containers/buildah>=1.20.0<=1.21.2
1.21.3
go/github.com/containers/buildah>=1.18.0<=1.19.8
1.19.9
go/github.com/containers/buildah>=1.17.0<=1.17.1
1.17.2
go/github.com/containers/buildah<=1.16.7
1.16.8
redhat/buildah<1.21.3
1.21.3
redhat/buildah<1.19.9
1.19.9
redhat/buildah<1.17.2
1.17.2
redhat/buildah<1.16.8
1.16.8
Buildah Project Buildah<1.16.8
Buildah Project Buildah>=1.17.0<1.17.2
Buildah Project Buildah>=1.19.0<1.19.9
Buildah Project Buildah>=1.21.0<1.21.3
redhat Enterprise Linux=8.0
redhat Enterprise Linux For Ibm Z Systems=8.0
redhat Enterprise Linux For Power Little Endian=8.0
debian/golang-github-containers-buildah<=1.19.6+dfsg1-1
1.28.2+ds1-3+deb12u11.39.3+ds1-11.42.1+ds1-2

Event History

Jun 8, 2021
Data Sourced
via Red Hat·05:43 AM
DescriptionSeverityAffected Software
Jul 19, 2021
Advisory Published
03:19 PM
Mar 3, 2022
CVE Published
via MITRE·06:26 PM
Data Sourced
via MITRE·06:26 PM
DescriptionWeakness
Data Sourced
via NVD·07:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Jan 11, 2024
Data Sourced
via Launchpad·11:57 PM
Description
Feb 24, 2026
Data Sourced
via Ubuntu·09:15 PM
RemedyDescriptionSeverityAffected Software
Data Sourced
via Debian·09:15 PM
DescriptionAffected Software

Frequently Asked Questions

1

What is the vulnerability ID for this Buildah flaw?

The vulnerability ID for this Buildah flaw is CVE-2021-3602.

2

What is the impact of the vulnerability?

The impact of the vulnerability is an information disclosure.

3

How does the vulnerability in Buildah occur?

The vulnerability in Buildah occurs when running processes using "chroot" isolation.

4

What is the severity of CVE-2021-3602?

The severity of CVE-2021-3602 is medium.

5

Which version of Buildah is affected by this vulnerability?

The versions affected by this vulnerability are 1.21.3, 1.19.9, 1.17.2, and 1.16.8.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203