Podman: WORKDIR symlink traversal vulnerability
podman-container-tools podman
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/containers/podman/v5 Go |
|
|
| github.com/containers/podman/v4 Go |
| No fix yet |
| github.com/containers/podman/v3 |
podman-container-tools podman
| Product | Affected | Fixed in |
|---|---|---|
| github.com/containers/podman/v5 Go |
|
|
| github.com/containers/podman/v4 Go |
| No fix yet |
| github.com/containers/podman/v3 |
|
| No fix yet |
| github.com/containers/podman Go |
| No fix yet |
| github.com/containers/podman/v2 Go |
| No fix yet |
Podman is a tool for managing OCI containers and pods. From 3.0.0 until 5.7.1, running a malicious container image where the WORKDIR path contains a symlink can create a directory or modify ownership on the host filesystem. Modified ownership is less likely to happen as that requires help from an untrusted/malicious process that mutates the host filesystem tree during dereferencing of the WORKDIR path, to trigger a race condition. This vulnerability is fixed in 5.7.1.
From the CVE record · GitHub_M
Podman can create a directory on the host filesystem when a user runs a malicious container image whose WORKDIR path contains a symlink. Host file ownership can also be changed, but that requires an untrusted process to mutate the host filesystem tree during path dereferencing to trigger a race condition.
Check installations of Podman before 5.7.1 and users of the affected Go packages: github.com/containers/podman/v5 before 5.7.1, plus the listed v4, v3, v2 and unversioned packages, which have no listed fix.