First published: Mon Feb 10 2020(Updated: )
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.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/podman | <0:1.6.4-7.el8 | 0:1.6.4-7.el8 |
Libpod Project Libpod | =1.6.0 | |
Redhat Openshift Container Platform | =4.3 | |
Redhat Enterprise Linux | =8.0 |
If a volume needs to be attached as read-only to an untrusted container or container image, first attach it to a trusted container. Using the volume for the first time will make the attack impossible for other containers that are going to use the volume.
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2020-1726 is a vulnerability discovered in Podman that allows containers to overwrite existing files in volumes, even if they are mounted as read-only.
CVE-2020-1726 has a severity rating of medium with a CVSS score of 5.9.
CVE-2020-1726 affects Podman by allowing containers to overwrite existing files in volumes.
To fix CVE-2020-1726, update Podman to version 1.6.4-7.el8 or later.
You can find more information about CVE-2020-1726 at the following references: [link1], [link2], [link3].