CVE-2024-3056
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.
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (0.55%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
Description
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 3.1
- 7.7 HIGHCVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:N/A:H
- EPSS
- 0.55% probability · 44th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-400
- Affected
- podman project/podman · redhat/openshift container platform · redhat/enterprise linux · fedoraproject/fedora
- Source
- secalert@redhat.com
References
- https://access.redhat.com/security/cve/CVE-2024-3056Third Party Advisory, Vendor Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=2270717Issue Tracking
- https://security.netapp.com/advisory/ntap-20241227-0002/
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.