Host file overwrite via symlinked Dockerfile write
Published Mar 31, 2020 · Updated Aug 4, 2024
Path traversal in Red Hat Buildah before 1.14.5 allows remote attackers to overwrite host files through a malicious build context. After a fetch failure, downloadToDirectory and stdinToDirectory can reuse a symlinked Dockerfile path and write the refetched body outside the build directory. Exploitation requires a user to build attacker-hosted HTTP(S) content; writes inherit that user's permissions and can alter files or enable code execution.
Summary
What happened
Path traversal in Red Hat Buildah before 1.14.5 allows remote attackers to overwrite host files through a malicious build context. After a fetch failure, downloadToDirectory and stdinToDirectory can reuse a symlinked Dockerfile path and write the refetched body outside the build directory. Exploitation requires a user to build attacker-hosted HTTP(S) content; writes inherit that user's permissions and can alter files or enable code execution.
The record
- CVE
- CVE-2020-10696
- Published
- Mar 31, 2020
- Updated
- Aug 4, 2024
- Vendor
- Red Hat
- Product
- Buildah
- Classifications
- CWE-22, T1204
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 31, 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=Fixed in buildah-1.14.5
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