Podman Project Podman 4.3.0

CPE Details

Podman Project Podman 4.3.0
podman_project
podman
4.3.0
2022-12-12
13h59 +00:00
2022-12-12
15h19 +00:00
CPE NVD
Alerte pour un CPE
Stay informed of any changes for a specific CPE.
Notifications manage

CPE Name: cpe:2.3:a:podman_project:podman:4.3.0:-:*:*:*:*:*:*

Informations

Vendor

podman_project

Product

podman

Version

4.3.0

Update

-

Related CVE

Open and find in CVE List

CVE ID Published Description Score Severity
CVE-2024-3056 2024-08-02 20h37 +00:00 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.
7.7
High
CVE-2022-4122 2022-12-07 23h00 +00:00 A vulnerability was found in buildah. Incorrect following of symlinks while reading .containerignore and .dockerignore results in information disclosure.
5.3
Medium
CVE-2022-4123 2022-12-07 23h00 +00:00 A flaw was found in Buildah. The local path and the lowest subdirectory may be disclosed due to incorrect absolute path traversal, resulting in an impact to confidentiality.
3.3
Low
CVE-2022-2989 2022-09-13 11h41 +00:00 An incorrect handling of the supplementary groups in the Podman container engine might lead to the sensitive information disclosure or possible data modification if an attacker has direct access to the affected container where supplementary groups are used to set access permissions and is able to execute a binary code in that container.
7.1
High