Arbitrary file write via unsanitized CPIO paths
Published Jun 24, 2020 · Updated Sep 17, 2024
Path traversal in SAS Institute go-rpmutils before 0.1.0 allows attackers to write files outside the extraction directory. The cpio.Extract function cleaned and joined each archive entry name without rejecting leading or embedded parent-directory segments. A consuming application must pass an attacker-controlled RPM or CPIO stream to Extract; resulting writes or overwrites carry the application's filesystem permissions.
Summary
What happened
Path traversal in SAS Institute go-rpmutils before 0.1.0 allows attackers to write files outside the extraction directory. The cpio.Extract function cleaned and joined each archive entry name without rejecting leading or embedded parent-directory segments. A consuming application must pass an attacker-controlled RPM or CPIO stream to Extract; resulting writes or overwrites carry the application's filesystem permissions.
The record
- CVE
- CVE-2020-7667
- Published
- Jun 24, 2020
- Updated
- Sep 17, 2024
- Vendor
- SAS Institute
- Product
- go-rpmutils
- Classifications
- CWE-22
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 24, 2020CVE publishedPublication date reported by the CVE source.
- Sep 17, 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=unspecified <0.1.0
What conditions does exploitation require?
What is affected?
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
- dotdot.cpio traversal regression fixtureproof of concept · demonstrated
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