Local secret disclosure via inherited chroot environments
Published Mar 3, 2022 · Updated Aug 3, 2024
Information disclosure in affected Buildah releases allows local users to read parent-process environment variables during chroot builds. The chroot/run.go launcher copied the entire Buildah environment into intermediate unshare commands instead of passing only its logging setting. Exploitation requires a process started by a RUN instruction or buildah run under chroot isolation; exposed values can include CI/CD registry credentials.
Summary
What happened
Information disclosure in affected Buildah releases allows local users to read parent-process environment variables during chroot builds. The chroot/run.go launcher copied the entire Buildah environment into intermediate unshare commands instead of passing only its logging setting. Exploitation requires a process started by a RUN instruction or buildah run under chroot isolation; exposed values can include CI/CD registry credentials.
The record
- CVE
- CVE-2021-3602
- Published
- Mar 3, 2022
- Updated
- Aug 3, 2024
- Vendor
- Containers
- Product
- Buildah
- Classifications
- CWE-212, CWE-200, T1552
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Mar 3, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Affects v1.21.2, v1.20.0, v1.19.8, v1.18.0, v1.17.1, v1.16.7, Fixed in v1.21.3, v1.19.9, v1.17.2, v1.16.8, v1.22.0 and above.
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo