Arbitrary file write via unjailed archive symlinks
Published Feb 24, 2020 · Updated Aug 4, 2024
Path traversal in Yarn before 1.22.0 allows remote attackers to write arbitrary files by inducing installation of a malicious package. The tarball fetcher passed attacker-controlled archive link targets to extraction without rebasing them inside the package directory, so crafted symlinks escaped that directory. A user must run yarn install on the package; the write occurs even with --ignore-scripts and can replace files writable by that user's account.
Summary
What happened
Path traversal in Yarn before 1.22.0 allows remote attackers to write arbitrary files by inducing installation of a malicious package. The tarball fetcher passed attacker-controlled archive link targets to extraction without rebasing them inside the package directory, so crafted symlinks escaped that directory. A user must run yarn install on the package; the write occurs even with --ignore-scripts and can replace files writable by that user's account.
The record
- CVE
- CVE-2020-8131
- Published
- Feb 24, 2020
- Updated
- Aug 4, 2024
- Vendor
- Yarn
- Product
- Yarn
- Classifications
- CWE-22, T1195.001, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 24, 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 Version: 1.22.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
- HackerOne malicious-package reproductionproof 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