Arbitrary file overwrite via symlinked node_modules
Published Aug 31, 2021 · Updated Aug 4, 2024
Symlink following in npm @npmcli/arborist before 2.8.2 allows attackers to write package contents to arbitrary filesystem locations. During dependency extraction, Arborist trusts an existing node_modules path and follows it when the directory has been replaced by a symbolic link. Exploitation requires another means to create that link, such as a preinstall script or a crafted repository that a user installs, and grants writes with the installing process's permissions.
Summary
What happened
Symlink following in npm @npmcli/arborist before 2.8.2 allows attackers to write package contents to arbitrary filesystem locations. During dependency extraction, Arborist trusts an existing node_modules path and follows it when the directory has been replaced by a symbolic link. Exploitation requires another means to create that link, such as a preinstall script or a crafted repository that a user installs, and grants writes with the installing process's permissions.
The record
- CVE
- CVE-2021-39135
- Published
- Aug 31, 2021
- Updated
- Aug 4, 2024
- Vendor
- npm
- Product
- @npmcli/arborist
- Classifications
- CWE-61, CWE-59, CAPEC-27, T1204.005
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 31, 2021CVE 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=< 2.8.2
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
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