File overwrite via unchecked volume copy-up
Published Feb 11, 2020 · Updated Aug 4, 2024
Improper volume handling in Podman 1.6.0 through 1.8.0 allows attackers to overwrite files when a container first uses a volume. In libpod/container_internal.go, mountNamedVolume copies image content into a named volume without checking whether the volume already contains data, including on read-only mounts. Running a malicious container or image against a previously unused Podman volume is required, and existing volume files can be replaced.
Summary
What happened
Improper volume handling in Podman 1.6.0 through 1.8.0 allows attackers to overwrite files when a container first uses a volume. In libpod/container_internal.go, mountNamedVolume copies image content into a named volume without checking whether the volume already contains data, including on read-only mounts. Running a malicious container or image against a previously unused Podman volume is required, and existing volume files can be replaced.
The record
- CVE
- CVE-2020-1726
- Published
- Feb 11, 2020
- Updated
- Aug 4, 2024
- Vendor
- Podman Container Tools
- Product
- Podman
- Classifications
- CWE-552, T1204.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 11, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=from 1.6.0 onwards
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo