CVE-2024-9675 high CVSS 7.8

Path Traversal in github.com/containers/buildah (CVE-2024-9675)

Summary

Path traversal in github.com/containers/buildah (CVE-2024-9675). Successful exploitation can lead to full system takeover. Exploitable via RUN. Mitigation: upgrade to 1.38.0 or later.

Original description

The description as published by the source.

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.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2024-9675 has been found in github.com/containers/buildah.
Attackers can target a specific entry point like RUN over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 7.8/10.
What to do: upgrade github.com/containers/buildah to 1.38.0 or later.
If unsure, ask your IT team or search "github.com/containers/buildah CVE-2024-9675" on the vendor's site.

CVE-2024-9675 (github.com/containers/buildah) — CWE-22 / CVSS v3 7.8
Attack vector: local / no user interaction
Attack surface: RUN
Patched: 1.38.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Path traversal (CWE-22) exists in github.com/containers/buildah. Attackers reach the vulnerable code path via RUN.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/containers/buildah. Attack surface: RUN.

🔥 Severity

Severity: High (CVSS 7.8/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 1.38.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/containers/buildah' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
grep -r 'github.com/containers/buildah' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/containers/buildah を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade github.com/containers/buildah to 1.38.0
```
ステージング環境で 1.38.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go github.com/containers/buildah

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.38.0"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

Debian DEBIAN-CVE-2024-9675 golang-github-containers-buildah