Podman has Files or Directories Accessible to External Parties
The podman
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/containers/podman Go |
|
|
| github.com/containers/podman/v2 Go |
|
|
| github.com/containers/libpod Go |
The podman
| Product | Affected | Fixed in |
|---|---|---|
| github.com/containers/podman Go |
|
|
| github.com/containers/podman/v2 Go |
|
|
| github.com/containers/libpod Go |
|
| No fix yet |
| github.com/containers/libpod/v2 Go |
|
|
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.
From the CVE record · redhat
Podman can allow a container to overwrite existing files in a volume mounted as read-only. This can happen when a user runs a malicious container, or one based on a malicious image, with an attached volume that is used for the first time.
Check installations using Go package github.com/containers/podman from 1.6.0 up to but not including 2.0.6, github.com/containers/podman/v2 or github.com/containers/libpod/v2 before 2.0.6, or github.com/containers/libpod from 1.6.0 onward.