cve.bz

CVE-2024-3056 Uncontrolled Resource Consumption

7.7 highEPSS 0.5%

High (7.7). EPSS 0.5% estimated probability of exploitation activity in the next 30 days.

On this page
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

CVSS 3.1

7.7 high
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:N/A:H
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 47th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2024-08-03. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-400 Uncontrolled Resource Consumption
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2024-3056 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-3056?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-3056?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-3056 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
podman_project:podmanthrough 5.2.0
redhat:openshift_container_platform4.0
redhat:enterprise_linux8.0
redhat:enterprise_linux9.0
fedoraproject:fedora40

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-rpcc-p8xm-rc6pGogithub.com/containers/podman/v5<=5.2.0no fix published
GHSA-rpcc-p8xm-rc6pGogithub.com/containers/podman<=5.2.0no fix published
GHSA-rpcc-p8xm-rc6pGogithub.com/containers/podman/v2<=5.2.0no fix published
GHSA-rpcc-p8xm-rc6pGogithub.com/containers/podman/v3<=5.2.0no fix published
GHSA-rpcc-p8xm-rc6pGogithub.com/containers/podman/v4<=5.2.0no fix published
GO-2024-3042Gogithub.com/containers/podmanall versionsno fix published
GO-2024-3042Gogithub.com/containers/podman/v2all versionsno fix published
GO-2024-3042Gogithub.com/containers/podman/v3all versionsno fix published
GO-2024-3042Gogithub.com/containers/podman/v4all versionsno fix published
GO-2024-3042Gogithub.com/containers/podman/v5all versionsno fix published

Linux distributions

DistributionReleasePackageFixed inAdvisory
UbuntuPro:22.04:LTS, Pro:24.04:LTSlibpodno fix listedUBUNTU-CVE-2024-3056
Azure Linux2podmanno fix listedAZL-49546
Azure Linux3podman5.6.1-2AZL-49596

From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Ubuntu.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

The vulnerability is not present in podman, but actually in the kernel. This is where any potential fix will be done and tracked.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelWill not fix
Red Hat Enterprise Linux 7kernelOut of support scope
Red Hat Enterprise Linux 7kernel-rtOut of support scope
Red Hat Enterprise Linux 7podmanOut of support scope
Red Hat Enterprise Linux 8container-tools:4.0/podmanNot affected
Red Hat Enterprise Linux 8container-tools:rhel8/podmanNot affected
Red Hat Enterprise Linux 8kernelWill not fix
Red Hat Enterprise Linux 8kernel-rtWill not fix
Red Hat Enterprise Linux 9kernelWill not fix
Red Hat Enterprise Linux 9podmanNot affected
Red Hat OpenShift Container Platform 3.11podmanOut of support scope
Red Hat OpenShift Container Platform 4podmanNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2024-3056.

Attack patterns (CAPEC)

  • CAPEC-147 XML Ping of the Death Likelihood: Low · Severity: Medium
  • CAPEC-227 Sustained Client Engagement
  • CAPEC-492 Regular Expression Exponential Blowup

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON