github.com/containers/buildah
Affected
- introduced
0, fixed1.16.8(semver)
Fixed versions
1.16.8
Fix
- Fixed version
1.16.8go get github.com/containers/[email protected]
Advisory
Also known as: CVE-2021-3602, GO-2022-0345
Buildah processes using chroot isolation may leak environment values to intermediate processes
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:
Medium Basis: The source's own band: MODERATE
0, fixed 1.16.8 (semver)1.16.8
1.16.8go get github.com/containers/[email protected]1.17.0, fixed 1.17.2 (semver)1.17.2
1.17.2go get github.com/containers/[email protected]1.18.0, fixed 1.19.9 (semver)1.19.9
1.19.9go get github.com/containers/[email protected]1.20.0, fixed 1.21.3 (semver)1.21.3
1.21.3go get github.com/containers/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0