CVE-2024-11218 - A vulnerability was found in podman build and buildah. This issue occurs in a container breakout by using
CVE-2024-11218 + A vulnerability was found in podman build and buildah. This issue occurs in a container breakout by using + High + 2025-01-22
One-sentence business risk
The vulnerable component sits in a commonly deployed application path and can create a material breach, outage, or compliance risk.
Research notes
- Root cause: A vulnerability was found in
podman buildandbuildah.This issue occurs in a container breakout by using --jobs=2 and a race condition when building a malicious Containerfile. - Affected versions: Affected versions named by the upstream advisory and dependency metadata.
- Fixed / safe versions: Vendor-fixed release or mitigation named by the upstream advisory.
- Public exploit / PoC signal: the consulted NVD/GHSA/vendor sources describe the trigger class; treat it as reproducible until patched.
- CVSS: 8.6 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H.
Exact vulnerable code pattern
update_or_read(request.body.target_id) # no owner/role check
Fixed / mitigated code pattern
target = load_owned_resource(actor, target_id); require_role(actor, target, "admin")
Dependency or runtime update:
rg -n "affected component|CVE-2024-11218" .
# update affected runtime/product to Vendor-fixed release or mitigation named by the upstream advisory
Step-by-step integration guide
- Inventory
affected componentacross source, lockfiles, SBOMs, container images, CI images, and deployment manifests. - Upgrade to
Vendor-fixed release or mitigation named by the upstream advisoryor apply the exact vendor patch referenced below. - Replace the vulnerable
authzpattern with the fixed pattern and fail closed on malformed input. - Add a regression test that exercises the advisory trigger and proves the request is rejected, bounded, or authorized.
- Deploy through canary, monitor security logs and resource metrics, then remove temporary edge blocks only after all runtimes are fixed.
Alternative mitigations
- Disable the vulnerable feature path while the package/runtime update rolls out.
- Add WAF or reverse-proxy rules for traversal tokens, prototype-polluting keys, oversized frames, shell metacharacters, or unauthenticated tool calls matching the trigger class.
- Restrict internal egress, rotate exposed secrets, and revoke affected tokens/keys if the vulnerability can disclose config, logs, JWT secrets, proxy credentials, or PKI material.
- For admin/API authorization issues, temporarily require elevated roles and explicit ownership checks at the gateway.
Detection signature
id: cve-2024-11218-a-vulnerability-was-found-in-podman-build-and-bu
source: NVD bulk JSON feed
dependency_or_product: "affected component"
affected: "Affected versions named by the upstream advisory and dependency metadata"
fixed: "Vendor-fixed release or mitigation named by the upstream advisory"
signals:
- "authz"
- "../"
- "__proto__"
- "tools/call"
- "wp_ajax_nopriv"
- "pickle.loads"
- "shell command construction"
action: "upgrade, add regression test, and verify deploy artifact"
Copy-paste skill
You are remediating CVE-2024-11218 (A vulnerability was found in podman build and buildah. This issue occurs in a container breakout by using) in this repository.
Find every affected dependency, runtime, image, service configuration, and reachable code path. Upgrade or patch to Vendor-fixed release or mitigation named by the upstream advisory. Replace the vulnerable authz pattern with a fail-closed implementation, add a regression test for the trigger shape, and update deployment/SBOM artifacts. If this repository does not control the affected runtime, create TRIAGE.md naming the owner, affected version, fixed version, and blocking decision.
Keywords, affected tech stack, and revenue tags
- Keywords:
CVE-2024-11218,authz,affected component,NVD bulk JSON feed. - Affected tech stack:
general. - Revenue tags:
sellable_to_fintech,enterprise_blocker,high_priority_sla.
References
- https://access.redhat.com/errata/RHSA-2025:0830
- https://access.redhat.com/errata/RHSA-2025:0878
- https://access.redhat.com/errata/RHSA-2025:0922
- https://access.redhat.com/errata/RHSA-2025:0923
- https://access.redhat.com/errata/RHSA-2025:1186
- https://access.redhat.com/errata/RHSA-2025:1187
- https://access.redhat.com/errata/RHSA-2025:1188
- https://access.redhat.com/errata/RHSA-2025:1189
- https://access.redhat.com/errata/RHSA-2025:1207
- https://access.redhat.com/errata/RHSA-2025:1275
- https://access.redhat.com/errata/RHSA-2025:1295
- https://access.redhat.com/errata/RHSA-2025:1296
- https://access.redhat.com/errata/RHSA-2025:1372
- https://access.redhat.com/errata/RHSA-2025:1453
- https://access.redhat.com/errata/RHSA-2025:1707
- https://access.redhat.com/errata/RHSA-2025:1713
- https://access.redhat.com/errata/RHSA-2025:1908
- https://access.redhat.com/errata/RHSA-2025:1910
- https://access.redhat.com/errata/RHSA-2025:1914
- https://access.redhat.com/errata/RHSA-2025:2441
- https://access.redhat.com/errata/RHSA-2025:2443
- https://access.redhat.com/errata/RHSA-2025:2454
- https://access.redhat.com/errata/RHSA-2025:2456
- https://access.redhat.com/errata/RHSA-2025:2701
- https://access.redhat.com/errata/RHSA-2025:2703
- https://access.redhat.com/errata/RHSA-2025:2710
- https://access.redhat.com/errata/RHSA-2025:2712
- https://access.redhat.com/errata/RHSA-2025:3577
- https://access.redhat.com/errata/RHSA-2025:3798
- https://access.redhat.com/security/cve/CVE-2024-11218
- https://bugzilla.redhat.com/show_bug.cgi?id=2326231
- https://github.com/containers/buildah/pull/5918
- https://nvd.nist.gov/vuln/detail/CVE-2024-11218