Buildah processes using chroot isolation may leak environment values to intermediate processes
Moderate severity
GitHub Reviewed
Published
Jul 15, 2021
in
containers/buildah
•
Updated Aug 29, 2023
Package
Affected versions
<= 1.16.7
>= 1.17.0, <= 1.17.1
>= 1.18.0, <= 1.19.8
>= 1.20.0, <= 1.21.2
Patched versions
1.16.8
1.17.2
1.19.9
1.21.3
Description
Reviewed
Jul 15, 2021
Published to the GitHub Advisory Database
Jul 19, 2021
Published by the National Vulnerability Database
Mar 3, 2022
Last updated
Aug 29, 2023
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 originalbuildah
process through its environment, that information will unintentionally be shared with child processes which it starts as part of handling RUN instructions or duringbuildah run
. The commands thatbuildah
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 underenv -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:
References