Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2024-11218 high CVSS 8.6

Privilege Escalation in podman build and buildah (CVE-2024-11218)

Summary

Vulnerability in podman build and buildah (CVE-2024-11218). Successful exploitation can lead to full system takeover. Exploitable via buildah..

Original description

The description as published by the source.

A vulnerability was found in podman build and buildah. This issue occurs in a container breakout by using --jobs=2 and a race condition when building a malicious Containerfile. SELinux might mitigate it, but even with SELinux on, it still allows the enumeration of files and directories on the host.

Source: NIST National Vulnerability Database NVD

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-11218 has been found in podman build and buildah.
Attackers can target a specific entry point like buildah. over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.6/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "podman build and buildah CVE-2024-11218" on the vendor's site.

CVE-2024-11218 (podman build and buildah) — CWE-269 / CVSS v3 8.6
Attack vector: local / unauthenticated
Attack surface: buildah.
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

A vulnerability (CWE-269) exists in podman build and buildah. Attackers reach the vulnerable code path via buildah. without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of podman build and buildah. Attack surface: buildah..

🔥 Severity

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

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ 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. Audit SBOM/dependencies to find affected services.

Response actions

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

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで podman build and buildah を使っているサービスとバージョンを洗い出す。

  2. 2
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details