CVE-2024-3056
Podman IPC DoS Vulnerability
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.
INFO
Published Date :
Aug. 2, 2024, 9:16 p.m.
Last Modified :
Oct. 16, 2024, 5:15 a.m.
Source :
[email protected]
Remotely Exploitable :
Yes !
Impact Score :
5.8
Exploitability Score :
1.3
Affected Products
The following products are affected by CVE-2024-3056
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2024-3056.
| URL | Resource |
|---|---|
| https://access.redhat.com/security/cve/CVE-2024-3056 | Third Party Advisory Vendor Advisory |
| https://bugzilla.redhat.com/show_bug.cgi?id=2270717 | Issue Tracking |
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2024-3056 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2024-3056 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by [email protected]
Oct. 16, 2024
Action Type Old Value New Value Removed CVSS V3.1 Red Hat, Inc. AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:N/A:H Added CVSS V3.1 Red Hat, Inc. AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:N/A:H -
Reanalysis by [email protected]
Oct. 04, 2024
Action Type Old Value New Value Removed CVSS V3.1 NIST AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H Added CVSS V3.1 NIST AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:N/A:H -
Initial Analysis by [email protected]
Sep. 23, 2024
Action Type Old Value New Value Added CVSS V3.1 NIST AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H Changed Reference Type https://access.redhat.com/security/cve/CVE-2024-3056 No Types Assigned https://access.redhat.com/security/cve/CVE-2024-3056 Third Party Advisory, Vendor Advisory Changed Reference Type https://bugzilla.redhat.com/show_bug.cgi?id=2270717 No Types Assigned https://bugzilla.redhat.com/show_bug.cgi?id=2270717 Issue Tracking Added CPE Configuration OR *cpe:2.3:a:podman_project:podman:*:*:*:*:*:*:*:* versions up to (including) 5.2.0 Added CPE Configuration OR *cpe:2.3:a:redhat:openshift_container_platform:4.0:*:*:*:*:*:*:* *cpe:2.3:o:redhat:enterprise_linux:8.0:*:*:*:*:*:*:* *cpe:2.3:o:redhat:enterprise_linux:9.0:*:*:*:*:*:*:* Added CPE Configuration OR *cpe:2.3:o:fedoraproject:fedora:40:*:*:*:*:*:*:* -
CVE Received by [email protected]
Aug. 02, 2024
Action Type Old Value New Value Added 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. Added Reference Red Hat, Inc. https://access.redhat.com/security/cve/CVE-2024-3056 [No types assigned] Added Reference Red Hat, Inc. https://bugzilla.redhat.com/show_bug.cgi?id=2270717 [No types assigned] Added CWE Red Hat, Inc. CWE-400 Added CVSS V3.1 Red Hat, Inc. AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:N/A:H
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2024-3056 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2024-3056
weaknesses.