Advisory

GHSA-rpcc-p8xm-rc6p

Also known as: CVE-2024-3056, GO-2024-3042

Summary

Podman vulnerable to memory-based denial of service

Details

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.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2024-08-02 21:31 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

github.com/containers/podman/v5

Go · All systems

Affected

  • introduced 0, last affected 5.2.0 (semver)

Fixed versions

None listed

Fix

No fixed version is listed.

github.com/containers/podman

Go · All systems

Affected

  • introduced 0, last affected 5.2.0 (semver)

Fixed versions

None listed

Fix

No fixed version is listed.

github.com/containers/podman/v2

Go · All systems

Affected

  • introduced 0, last affected 5.2.0 (semver)

Fixed versions

None listed

Fix

No fixed version is listed.

github.com/containers/podman/v3

Go · All systems

Affected

  • introduced 0, last affected 5.2.0 (semver)

Fixed versions

None listed

Fix

No fixed version is listed.

github.com/containers/podman/v4

Go · All systems

Affected

  • introduced 0, last affected 5.2.0 (semver)

Fixed versions

None listed

Fix

No fixed version is listed.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences