CVE-2024-3056: 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 ...

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.

Metrics

CVSS 3.1

7.7/10

CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:N/A:H

EPSS Probability

0.51%

39.8th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

CWE-400

Affected Software

Vendor	Product	Versions
Podman Project	Podman	<= 5.2.0
Redhat	Openshift Container Platform	4.0
Redhat	Enterprise Linux	8.0
Redhat	Enterprise Linux	9.0
Fedoraproject	Fedora	40

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/

Timeline

Published: Aug 2, 2024
Last Modified: Jun 17, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2024-3056?

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.

How severe is CVE-2024-3056?

CVE-2024-3056 has a CVSS score of 7.7/10 (HIGH severity). The EPSS model estimates a 0.51% probability of exploitation in the next 30 days.

How do I fix CVE-2024-3056?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.