# CVE-2024-3056: Podman: kernel: containers in shared ipc namespace are vulnerable to denial of service attack > An attacker can cause a system-wide memory denial of service by exploiting IPC namespace sharing in Podman containers. - **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 2 Aug 2024 - **Updated:** 29 Oct 2026 - **Also known as:** AZL-49546, AZL-49596, GHSA-rpcc-p8xm-rc6p, GO-2024-3042, MINI-8cv2-gxm6-975c, UBUNTU-CVE-2024-3056 ## What is CVE-2024-3056? CVE-2024-3056 is a high-severity denial of service vulnerability in Fedoraproject Fedora, published on 2 Aug 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. ### Official 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. Weakness: CWE-400 (Uncontrolled Resource Consumption) ## Which versions are affected by CVE-2024-3056? 15 open source packages ship an affected version, including github.com/containers/podman, github.com/containers/podman/v2 and github.com/containers/podman/v3. It affects 4 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/containers/podman` | Go | All versions | None | | `github.com/containers/podman` | Go | All versions to 5.2.0 | None | | `github.com/containers/podman` | Go | All versions to 5.2.0 | None | | `github.com/containers/podman/v2` | Go | All versions | None | | `github.com/containers/podman/v2` | Go | All versions to 5.2.0 | None | | `github.com/containers/podman/v2` | Go | All versions to 5.2.0 | None | | `github.com/containers/podman/v3` | Go | All versions | None | | `github.com/containers/podman/v3` | Go | All versions to 5.2.0 | None | | `github.com/containers/podman/v3` | Go | All versions to 5.2.0 | None | | `github.com/containers/podman/v4` | Go | All versions | None | | `github.com/containers/podman/v4` | Go | All versions to 5.2.0 | None | | `github.com/containers/podman/v4` | Go | All versions to 5.2.0 | None | | `github.com/containers/podman/v5` | Go | All versions | None | | `github.com/containers/podman/v5` | Go | All versions to 5.2.0 | None | | `github.com/containers/podman/v5` | Go | All versions to 5.2.0 | None | Products: Fedoraproject Fedora, Podman Project Podman, Redhat Enterprise Linux, Redhat Openshift Container Platform. ## How do I fix CVE-2024-3056? Apply the vendor's patch. ## Is CVE-2024-3056 being exploited? There is no known exploitation of CVE-2024-3056 in the wild and no public exploit code. ## Other vulnerabilities in Fedoraproject Fedora - [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild) - [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild) - [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild) - [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild) - [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-3056 and fix it if it is affected. What it is: CVE-2024-3056 is a high-severity denial of service vulnerability in Fedoraproject Fedora, published on 2 Aug 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2024-3056 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/containers/podman (Go): affected all versions; no fix listed - github.com/containers/podman (Go): affected all versions up to 5.2.0; no fix listed - github.com/containers/podman (Go): affected all versions up to 5.2.0; no fix listed - github.com/containers/podman/v2 (Go): affected all versions; no fix listed - github.com/containers/podman/v2 (Go): affected all versions up to 5.2.0; no fix listed - github.com/containers/podman/v2 (Go): affected all versions up to 5.2.0; no fix listed - github.com/containers/podman/v3 (Go): affected all versions; no fix listed - github.com/containers/podman/v3 (Go): affected all versions up to 5.2.0; no fix listed - github.com/containers/podman/v3 (Go): affected all versions up to 5.2.0; no fix listed - github.com/containers/podman/v4 (Go): affected all versions; no fix listed - github.com/containers/podman/v4 (Go): affected all versions up to 5.2.0; no fix listed - github.com/containers/podman/v4 (Go): affected all versions up to 5.2.0; no fix listed Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-3056/ (Markdown: https://insights.sbomify.com/CVE-2024-3056/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-3056 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-3056 - OSV: https://osv.dev/vulnerability/CVE-2024-3056 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-3056/ Summaries are generated and may contain mistakes; the official description above is the record.