Filtered by vendor Libpod Project Subscriptions
Filtered by product Libpod Subscriptions
Total 5 CVE
CVE Vendors Products Updated CVSS v3.1
CVE-2018-10856 2 Libpod Project, Redhat 2 Libpod, Rhel Extras Other 2024-08-05 N/A
It has been discovered that podman before version 0.6.1 does not drop capabilities when executing a container as a non-root user. This results in unnecessary privileges being granted to the container.
CVE-2019-18466 2 Libpod Project, Redhat 3 Libpod, Enterprise Linux, Rhel Extras Other 2024-08-05 5.5 Medium
An issue was discovered in Podman in libpod before 1.6.0. It resolves a symlink in the host context during a copy operation from the container to the host, because an undesired glob operation occurs. An attacker could create a container image containing particular symlinks that, when copied by a victim user to the host filesystem, may overwrite existing files with others from the host.
CVE-2019-10214 5 Buildah Project, Libpod Project, Opensuse and 2 more 7 Buildah, Libpod, Leap and 4 more 2024-08-04 5.9 Medium
The containers/image library used by the container tools Podman, Buildah, and Skopeo in Red Hat Enterprise Linux version 8 and CRI-O in OpenShift Container Platform, does not enforce TLS connections to the container registry authorization service. An attacker could use this vulnerability to launch a MiTM attack and steal login credentials or bearer tokens.
CVE-2019-10152 3 Libpod Project, Opensuse, Redhat 3 Libpod, Leap, Rhel Extras Other 2024-08-04 7.2 High
A path traversal vulnerability has been discovered in podman before version 1.4.0 in the way it handles symlinks inside containers. An attacker who has compromised an existing container can cause arbitrary files on the host filesystem to be read/written when an administrator tries to copy a file from/to the container.
CVE-2020-1726 2 Libpod Project, Redhat 4 Libpod, Enterprise Linux, Openshift and 1 more 2024-08-04 5.9 Medium
A flaw was discovered in Podman where it incorrectly allows containers when created to overwrite existing files in volumes, even if they are mounted as read-only. When a user runs a malicious container or a container based on a malicious image with an attached volume that is used for the first time, it is possible to trigger the flaw and overwrite files in the volume.This issue was introduced in version 1.6.0.