CVE-2024-3056
mediumpriority · track · 0EPSS 0.005 · 46 %ileDEEURUUSEPSS · scored 2026-10-27
A flaw was found in Podman. This issue may allow an attacker to create a specially crafted container that, when configured to share the same IPC with at least one other container, can create a large number of IPC resources in /dev/shm. The malicious container will continue to exhaust resources until it is out-of-memory (OOM) killed. While the malicious container's cgroup will be removed, the IPC resources it created are not. Those resources are tied to the IPC namespace that will not be removed until all containers using it are stopped, and one non-malicious container is holding the namespace open. The malicious container is restarted, either automatically or by attacker control, repeating the process and increasing the amount of memory consumed. With a container configured to restart always, such as `podman run --restart=always`, this can result in a memory-based denial of service of the system.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · medium–high · 4.8–7.7
ssvc
A stakeholder decision — act, attend, or track — from exploitation and impact.
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (22)
Products and version ranges known to be affected.
- redhat openshift container platform= 4.0nvdUScpe:2.3:a:redhat:openshift_container_platform:*:*:*:*:*:*:*:*
advisories (3)
Vendor and ecosystem advisories describing this.
- WID-SEC-W-2024-1766Podman: Schwachstelle ermöglicht Denial of ServiceDeutsch2024-08-05csaf · cert_bundDE
Ein entfernter, authentisierter Angreifer kann eine Schwachstelle in Podman ausnutzen, um einen Denial of Service Angriff durchzuführen.
- GHSA-rpcc-p8xm-rc6pPodman vulnerable to memory-based denial of service2024-08-02ghsa · osvUS
A flaw was found in Podman. This issue may allow an attacker to create a specially crafted container that, when configured to share the same IPC with at least one other container, can create a large number of IPC resources in /dev/shm. The malicious container will continue to exhaust resources until it is out-of-memory (OOM) killed. While the malicious container's cgroup will be removed, the IPC resources it created are not. Those resources are tied to the IPC namespace that will not be removed until all containers using it are stopped, and one non-malicious container is holding the namespace open. The malicious container is restarted, either automatically or by attacker control, repeating the process and increasing the amount of memory consumed. With a container configured to restart always, such as `podman run --restart=always`, this can result in a memory-based denial of service of the system.
- GO-2024-3042Podman vulnerable to memory-based denial of service in github.com/containers/podman2024-08-06vendor · osvUS
Podman vulnerable to memory-based denial of service in github.com/containers/podman
also known as (6)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (9)
External citations — patches, advisories, analysis.
- https://access.redhat.com/security/cve/CVE-2024-3056cnnvd
- https://bugzilla.redhat.com/show_bug.cgi?id=2270717cnnvd
- https://cxsecurity.com/cveshow/CVE-2024-3056/cnnvd
- https://github.com/containers/podman/releases/tag/v5.2.0Patchcnnvd
- https://access.redhat.com/security/cve/CVE-2024-3056enisa_euvd
- https://bugzilla.redhat.com/show_bug.cgi?id=2270717enisa_euvd
- https://access.redhat.com/security/cve/CVE-2024-3056Third Party AdvisoryVendor Advisorynvd
- https://bugzilla.redhat.com/show_bug.cgi?id=2270717Issue Trackingnvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan