CVE-2024-9675: Buildah: buildah allows arbitrary directory mount
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.
Security readout for executives and security teams
Plain-English summary
Buildah can let a container build file mount a host directory into the build container when cache mount paths are not properly constrained. If a malicious or untrusted build runs under a user with access to sensitive host files, those files could be read or changed.
Executive priority
Treat as high priority where container builds cross trust boundaries. The main business risk is leakage or modification of host-accessible files from build infrastructure, not remote internet compromise by itself.
Technical view
CVE-2024-9675 is a CWE-22 path validation issue in Buildah cache mounts. A RUN instruction can mount an arbitrary host directory read/write into the container, limited by the permissions of the user running Buildah. Red Hat lists affected Buildah, Podman, container-tools, and OpenShift builder packages.
Likely exposure
Exposure is most likely in CI/CD, image build workers, developer workstations, and OpenShift build environments that process untrusted or semi-trusted Containerfiles using affected Red Hat Buildah, Podman, container-tools, or ose-docker-builder packages.
Exploitation context
The CVSS vector is local, low complexity, low privilege, and no user interaction. The source bundle says KEV is false and provides no evidence of active exploitation. The attacker needs a way to influence a build file executed by affected tooling.
Researcher notes
Do not assume full host compromise beyond the build user’s file permissions. The key validation question is whether an attacker can control a RUN cache mount path in a build executed by affected tooling.
Mitigation direction
Apply the relevant Red Hat security advisory updates for installed packages.
Prioritize shared build hosts and CI runners processing untrusted Containerfiles.
Restrict who can submit or modify container build definitions.
Run builds with least-privileged accounts and isolated workers.
Check vendor guidance before applying non-vendor workarounds.
Validation and detection
Inventory Buildah, Podman, container-tools, and ose-docker-builder versions.
Compare installed versions with the Red Hat affected package list.
Identify CI jobs or OpenShift builds accepting external Containerfiles.
Confirm updated packages are deployed on all build workers.
Review build-worker host file permissions for sensitive accessible paths.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-22 · source CWE mapping
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.