Buildahproject Buildah
Don't miss out!
Thousands of developers use stack.watch to stay informed.Get an email whenever new security vulnerabilities are reported in Buildahproject Buildah.
By the Year
In 2025 there have been 0 vulnerabilities in Buildahproject Buildah. Last year, in 2024 Buildah had 1 security vulnerability published. Right now, Buildah is on track to have less security vulnerabilities in 2025 than it did last year.
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2025 | 0 | 0.00 |
| 2024 | 1 | 7.80 |
| 2023 | 0 | 0.00 |
| 2022 | 3 | 6.47 |
| 2021 | 0 | 0.00 |
| 2020 | 1 | 8.80 |
| 2019 | 1 | 5.90 |
| 2018 | 0 | 0.00 |
It may take a day or so for new Buildah vulnerabilities to show up in the stats or in the list of recent security vulnerabilties. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Buildahproject Buildah Security Vulnerabilities
A vulnerability was found in Buildah
CVE-2024-9675
7.8 - High
- October 09, 2024
A vulnerability was found in Buildah. Cache mounts do not properly validate that user-specified paths for the cache are within our cache directory, allowing a `RUN` instruction in a Container file to mount an arbitrary directory from the host (read/write) into the container as long as those files can be accessed by the user running Buildah.
Directory traversal
An incorrect handling of the supplementary groups in the Buildah container engine might lead to the sensitive information disclosure or possible data modification if an attacker has direct access to the affected container where supplementary groups are used to set access permissions and is able to execute a binary code in
CVE-2022-2990
7.1 - High
- September 13, 2022
An incorrect handling of the supplementary groups in the Buildah container engine might lead to the sensitive information disclosure or possible data modification if an attacker has direct access to the affected container where supplementary groups are used to set access permissions and is able to execute a binary code in that container.
Placement of User into Incorrect Group
A flaw was found in buildah where containers were incorrectly started with non-empty default permissions
CVE-2022-27651
6.8 - Medium
- April 04, 2022
A flaw was found in buildah where containers were incorrectly started with non-empty default permissions. A bug was found in Moby (Docker Engine) where containers were incorrectly started with non-empty inheritable Linux process capabilities, enabling an attacker with access to programs with inheritable file capabilities to elevate those capabilities to the permitted set when execve(2) runs. This has the potential to impact confidentiality and integrity.
Incorrect Default Permissions
An information disclosure flaw was found in Buildah, when building containers using chroot isolation
CVE-2021-3602
5.5 - Medium
- March 03, 2022
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).
Improper Removal of Sensitive Information Before Storage or Transfer
A path traversal flaw was found in Buildah in versions before 1.14.5
CVE-2020-10696
8.8 - High
- March 31, 2020
A path traversal flaw was found in Buildah in versions before 1.14.5. This flaw allows an attacker to trick a user into building a malicious container image hosted on an HTTP(s) server and then write files to the user's system anywhere that the user has permissions.
Directory traversal
The containers/image library used by the container tools Podman
CVE-2019-10214
5.9 - Medium
- November 25, 2019
The containers/image library used by the container tools Podman, Buildah, and Skopeo in Red Hat Enterprise Linux version 8 and CRI-O in OpenShift Container Platform, does not enforce TLS connections to the container registry authorization service. An attacker could use this vulnerability to launch a MiTM attack and steal login credentials or bearer tokens.
Insufficiently Protected Credentials
Stay on top of Security Vulnerabilities
Want an email whenever new vulnerabilities are published for OpenSuse Leap or by Buildahproject? Click the Watch button to subscribe.
