@npmcli/arborist 0.0.20 vulnerabilities

Known vulnerabilities in the @npmcli/arborist package. This does not include vulnerabilities belonging to this package’s dependencies.

Vulnerability	Vulnerable Version
H Arbitrary File Write @npmcli/arborist is a Manage node_modules trees Affected versions of this package are vulnerable to Arbitrary File Write. `@npmcli/arborist` 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, in part, accomplished by resolving dependency specifiers defined in `package.json` manifests for dependencies with a specific name, and nesting folders to resolve conflicting dependencies. When multiple dependencies differ only in the case of their name, `Arborist`'s internal data structure sees them as separate items that could coexist within the same level in the `node_modules` hierarchy. However, on case-insensitive file systems (such as macOS and Windows), this is not the case. Combined with a symlink dependency such as `file:/some/path`, this allows an attacker to create a situation in which arbitrary contents could be written to any location on the filesystem. How to fix Arbitrary File Write? Upgrade `@npmcli/arborist` to version 2.8.2 or higher.	<2.8.2
H Arbitrary File Write @npmcli/arborist is a Manage node_modules trees Affected versions of this package are vulnerable to Arbitrary File Write. `@npmcli/arborist` 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. How to fix Arbitrary File Write? Upgrade `@npmcli/arborist` to version 2.8.2 or higher.	<2.8.2

Vulnerability

Vulnerable Version

Arbitrary File Write

@npmcli/arborist is a Manage node_modules trees

Affected versions of this package are vulnerable to Arbitrary File Write. @npmcli/arborist 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, in part, accomplished by resolving dependency specifiers defined in package.json manifests for dependencies with a specific name, and nesting folders to resolve conflicting dependencies.

When multiple dependencies differ only in the case of their name, Arborist's internal data structure sees them as separate items that could coexist within the same level in the node_modules hierarchy. However, on case-insensitive file systems (such as macOS and Windows), this is not the case. Combined with a symlink dependency such as file:/some/path, this allows an attacker to create a situation in which arbitrary contents could be written to any location on the filesystem.

How to fix Arbitrary File Write?

Upgrade @npmcli/arborist to version 2.8.2 or higher.

<2.8.2

Arbitrary File Write

@npmcli/arborist is a Manage node_modules trees

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.

How to fix Arbitrary File Write?

Upgrade @npmcli/arborist to version 2.8.2 or higher.

<2.8.2

@npmcli/arborist/.../arborist@0.0.20 vulnerabilities

Manage node_modules trees

latest version

latest non vulnerable version

first published

latest version published

licenses detected

Direct Vulnerabilities

How to fix?