@npmcli/arborist, the library that calculates dependency trees and manages the node_modules folder hierarchy for the npm command line interface, aims to guarantee that package dependency contracts will be met, and the extraction of package contents will always be performed into the expected folder. This is accomplished by extracting package contents into a project's node_modules folder. If the node_modules folder of the root project or any of its dependencies is somehow replaced with a symbolic link, it could allow Arborist to write package dependencies to any arbitrary location on the file system. Note that symbolic links contained within package artifact contents are filtered out, so another means of creating a node_modules symbolic link would have to be employed. A preinstall script could replace node_modules with a symlink. (This is prevented by using --ignore-scripts.) An attacker could supply the target with a git repository, instructing them to run npm install --ignore-scripts in the root. This may be successful, because npm install --ignore-scripts is typically not capable of making changes outside of the project directory, so it may be deemed safe. Reference: https://github.com/npm/arborist/security/advisories/GHSA-gmw6-94gg-2rc2
Searched Red Hat - This CVE page does not exist - https://access.redhat.com/security/cve/CVE-2021-39135 Any idea when Red Hat will open a CVE record and include this fix?
Upstream fix: https://github.com/npm/arborist/commit/041a3c710c2a6fbf644fc2c1119f7f0f440ffadd https://github.com/npm/arborist/commit/f2b0ceebfe94123f162c3652af46f9c4c473cc36
In reply to comment #2: > Searched Red Hat - This CVE page does not exist - > https://access.redhat.com/security/cve/CVE-2021-39135 > > Any idea when Red Hat will open a CVE record and include this fix? The page should now exist
* npm versions v7 until older than v7.21.0 are affected * npm versions v7.21.0 and newer (including v8.0.0) are not affected * npm versions 6.x and older are not using @npmcli/arborist, and thus are not affected
Created nodejs:16/nodejs tracking bugs for this issue: Affects: fedora-all [bug 2029557]