github.com/containers/podman/v5

CVE-2024-3056

CVE-2024-3056 is a high-severity uncontrolled resource consumption vulnerability in github.com/containers/podman/v5 (go), affecting versions <= 5.2.0. No fixed version is listed yet.

Key facts
CVSS score
4.8
High
Attack vector
Network
Issuing authority
GitHub Advisory Database
Affected package
github.com/containers/podman/v5
Fixed in
Not available
Disclosed
2024

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.

Impact

What is uncontrolled resource consumption?

Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.

Severity and exposure

CVE-2024-3056 has a CVSS score of 4.8 (High). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.

No fixed version is listed yet, so configuration controls and monitoring matter more in the interim.

Affected versions

go

  • github.com/containers/podman/v5 (<= 5.2.0)
  • github.com/containers/podman (<= 5.2.0)
  • github.com/containers/podman/v2 (<= 5.2.0)
  • github.com/containers/podman/v3 (<= 5.2.0)
  • github.com/containers/podman/v4 (<= 5.2.0)

Security releases

Not available
Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.

Kodem's runtime-powered SCA identifies whether CVE-2024-3056 is reachable in your applications. Explore open-source security for your team.

See if CVE-2024-3056 is reachable in your applications. Get a demo

Remediation advice

No fixed version is listed for CVE-2024-3056 yet.

In the interim: Apply input size limits and request rate limiting. Reject input that exceeds reasonable bounds before processing begins.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently asked questions about CVE-2024-3056

What is CVE-2024-3056?

CVE-2024-3056 is a high-severity uncontrolled resource consumption vulnerability in github.com/containers/podman/v5 (go), affecting versions <= 5.2.0. No fixed version is listed yet. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.

How severe is CVE-2024-3056?

CVE-2024-3056 has a CVSS score of 4.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which packages are affected by CVE-2024-3056?
  • github.com/containers/podman/v5 (go) (versions <= 5.2.0)
  • github.com/containers/podman (go) (versions <= 5.2.0)
  • github.com/containers/podman/v2 (go) (versions <= 5.2.0)
  • github.com/containers/podman/v3 (go) (versions <= 5.2.0)
  • github.com/containers/podman/v4 (go) (versions <= 5.2.0)
Is there a fix for CVE-2024-3056?

No fixed version is listed for CVE-2024-3056 yet. Monitor the advisory for updates and apply mitigations in the interim.

Is CVE-2024-3056 exploitable, and should I be worried?

Whether CVE-2024-3056 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo

What actually determines whether CVE-2024-3056 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2024-3056?

No fixed version is listed yet. In the interim: Apply input size limits and request rate limiting. Reject input that exceeds reasonable bounds before processing begins.

Stop the waste.
Protect your environment with Kodem.