CVE-2024-3056
published 2024-08-02CVE-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…
PriorityP422medium4.8CVSS 3.1
AVNACHPRLUIRSUCNINAH
EPSS
0.55%
42.4th percentile
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.
Affected
10 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| fedoraproject | fedora | — | — |
| github.com | containers_podman | 0 – 5.2.0 | — |
| github.com | containers_podman_v2 | 0 – 5.2.0 | — |
| github.com | containers_podman_v3 | 0 – 5.2.0 | — |
| github.com | containers_podman_v4 | 0 – 5.2.0 | — |
| github.com | containers_podman_v5 | 0 – 5.2.0 | — |
| podman_project | podman | <= 5.2.0 | — |
| redhat | enterprise_linux | — | — |
| redhat | enterprise_linux | — | — |
| redhat | openshift_container_platform | — | — |
CVSS provenance
nvdv3.14.8MEDIUMCVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:N/A:H
osv4.8MEDIUM
vendor_redhat7.7HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
Podman vulnerable to memory-based denial of service in github.com/containers/podman
osv·2024-08-06
CVE-2024-3056 Podman vulnerable to memory-based denial of service in github.com/containers/podman
Podman vulnerable to memory-based denial of service in github.com/containers/podman
Podman vulnerable to memory-based denial of service in github.com/containers/podman
GHSA
Podman vulnerable to memory-based denial of service
ghsa·2024-08-02
CVE-2024-3056 [HIGH] CWE-400 Podman vulnerable to memory-based denial of service
Podman vulnerable to memory-based denial of service
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
OSV
Podman vulnerable to memory-based denial of service
osv·2024-08-02
CVE-2024-3056 [HIGH] Podman vulnerable to memory-based denial of service
Podman vulnerable to memory-based denial of service
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
OSV
CVE-2024-3056: A flaw was found in Podman
osv·2024-08-02·CVSS 4.8
CVE-2024-3056 [MEDIUM] CVE-2024-3056: A flaw was found in Podman
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 alwa
Red Hat
podman: kernel: containers in shared IPC namespace are vulnerable to denial of service attack
vendor_redhat·2024-07-25·CVSS 7.7
CVE-2024-3056 [HIGH] CWE-400 podman: kernel: containers in shared IPC namespace are vulnerable to denial of service attack
podman: kernel: containers in shared IPC namespace are vulnerable to denial of service attack
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 pr
No detection rules found.
No public exploits indexed.
2024-08-02
Published