Podman has Files or Directories Accessible to External Parties
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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2020-1726US | medium5.9 | — | ||
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… | ||||
02
references
External citations — patches, advisories, analysis.
- http://lists.opensuse.org/opensuse-security-announce/2020-09/msg00097.htmlWEB
- http://lists.opensuse.org/opensuse-security-announce/2020-09/msg00103.htmlWEB
- https://access.redhat.com/errata/RHSA-2020:0680WEB
- https://access.redhat.com/errata/RHSA-2020:1650WEB
- https://access.redhat.com/security/cve/CVE-2020-1726WEB
- https://bugzilla.redhat.com/show_bug.cgi?id=1801152WEB
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-1726WEB
- https://github.com/containers/podmanPACKAGE
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan