Podman: kernel: containers in shared ipc namespace are vulnerable to denial of service attack
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- podman
5.0.0
- kernel
Version range not reported
- kernel
Version range not reported
- kernel-rt
Version range not reported
- podman
Version range not reported
- container-tools:4.0/podman
Version range not reported
- container-tools:rhel8/podman
Version range not reported
- kernel
Version range not reported
- kernel-rt
Version range not reported
- kernel
Version range not reported
- podman
Version range not reported
- podman
Version range not reported
- podman
Version range not reported
- github.com/containers/podman/v5Go
through 5.2.0
- github.com/containers/podmanGo
through 5.2.0
- github.com/containers/podman/v2Go
through 5.2.0
- github.com/containers/podman/v3Go
through 5.2.0
- github.com/containers/podman/v4Go
through 5.2.0
- github.com/containers/podmanGo
All versions
- github.com/containers/podman/v2Go
All versions
- github.com/containers/podman/v3Go
All versions
- github.com/containers/podman/v4Go
All versions
- github.com/containers/podman/v5Go
All versions