CVE-2019-18466: Medium severity libpod vulnerability
'podman cp' will resolve a carefully crafted symlink in host-filesystem space, yielding unexpected results when cp'ing from container to host. 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.
Upstream Issue: https://github.com/containers/libpod/issues/3829
Other sources
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.
It was discovered that podman resolves a symlink in the host context during a copy operation from the container to the host. 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.
Affected Software
Remediation
Patch Available
Event History
Parent advisories
This vulnerability appears in the following advisories.
Frequently Asked Questions
What is CVE-2019-18466?
CVE-2019-18466 is a vulnerability discovered in Podman in libpod before 1.6.0.
What is the severity of CVE-2019-18466?
CVE-2019-18466 has a severity rating of medium with a CVSS score of 5.5.
How does CVE-2019-18466 affect Podman?
CVE-2019-18466 affects Podman in libpod before version 1.6.0.
How can an attacker exploit CVE-2019-18466?
An attacker can create a container image containing specific symlinks that, when copied, can lead to a symlink resolution vulnerability in Podman.
Is there a fix for CVE-2019-18466?
Yes, the remedy for CVE-2019-18466 is to upgrade to version 1.6.0 of libpod.