podman: incorrectly allows existing files in volumes to be overwritten by a container when it is created
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| The | podman | affected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat Enterprise Linux 8 | |||
| container-tools:rhel8-8020020200324071414.0d58ad57 | cpe:/a:redhat:enterprise_linux:8 | RHSA-2020:1650 | 2020-04-28T00:00:00Z |
| Red Hat OpenShift Container Platform 4.3 | |||
| podman-0:1.6.4-7.el8 | cpe:/a:redhat:openshift:4.3::el8 | RHSA-2020:0680 | 2020-03-10T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2022-5384 | 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. |
Github GHSA |
GHSA-vmhj-p9hw-vgrf | Podman has Files or Directories Accessible to External Parties |
No CVSS v4.0
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 1.5% (1.526% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.