Vulnerabilities in pkg:npm/@npmcli/arborist

PACKAGE
Advisory Identifier: GHSA-2h3h-q99f-3fhc
Advisory Summary

CVE-2021-39134 is a HIGH (CVSS 8.2) @npmcli/arborist vulnerable to unix symbolic vulnerability (CWE-59: Improper Link Resolution Before File Access ('Link Following')) affecting @npmcli/arborist libraries in the npm ecosystem. The issue involves @npmcli/arborist vulnerable to unix symbolic link (symlink) following. Remediation is available by upgrading affected packages to version 2.8.2.

2 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:npm/@npmcli/arborist

2 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:npm/@npmcli/arborist. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-2h3h-q99f-3fhc CVE-2021-39134 HIGH @npmcli/arborist vulnerable to UNIX Symbolic Link (Symlink) Following
GHSA-gmw6-94gg-2rc2 CVE-2021-39135 HIGH UNIX Symbolic Link (Symlink) Following in @npmcli/arborist

CVE-2021-39134 at a Glance

CVE Identifier CVE-2021-39134
GHSA Identifier GHSA-2h3h-q99f-3fhc
Severity HIGH
CVSS v3.1 Base Score 8.2
CWE Classification CWE-59: Improper Link Resolution Before File Access ('Link Following')
Affected Product @npmcli/arborist
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 8.2

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N).

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Changed (S:C)
Confidentiality High (C:H)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2021-39134

To remediate this vulnerability, upgrade all affected @npmcli/arborist dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

@npmcli/arborist fixed: 2.8.2
npm install @npmcli/arborist@2.8.2
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls @npmcli/arborist

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2021-39134, inspect your project dependencies using npm:

npm ls @npmcli/arborist

Analyze the terminal output to locate any version of @npmcli/arborist in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.8.2), your application is affected.

Note: The npm ls @npmcli/arborist command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-59: Improper Link Resolution Before File Access ('Link Following'), where the product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource. In @npmcli/arborist, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact Arbitrary File Creation, Arbitrary File Overwrite, Arbitrary Code Execution `@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, 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 saw 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 allowed an attacker to create a situation in which arbitrary contents could be written to any location on the filesystem. For example, a package `pwn-a` could define a dependency in their `package.json` file such as `"foo": "file:/some/path"`. Another package, `pwn-b` could define a dependency such as `FOO: "file:foo.tgz"`. On case-insensitive file systems, if `pwn-a` was installed, and then `pwn-b` was installed afterwards, the contents of `foo.tgz` would be written to `/some/path`, and any existing contents of `/some/path` would be removed. Anyone using npm v7.20.6 or earlier on a case-insensitive filesystem is potentially affected. ### Patches 2.8.2 (included in npm v7.20.7 and above) ### Fix and Caveats There are two parts to the fix: 1. Immediately prior to extraction, if the target folder is not a directory, it is moved aside. (If the installation fails, filesystem entries moved aside in this manner are moved back as part of the rollback process.) 2. The `children` map that represents child nodes in the tree is replaced with a case-insensitive map object, such that `node.children.get('foo')` and `node.children.get('FOO')` will return the same object, enabling Arborist to detect and handle this class of tree collision. This second item imposes a caveat on case _sensitive_ filesystems where two packages with names which differ only in case may already exist at the same level in the tree, causing unpredictable behavior in this rare edge case. Note that in such cases, the `package-lock.json` already creates a situation which is hazardous to use on case-sensitive filesystems, and will likely lead to other problems. If affected by this caveat, please run `npm update` to rebuild your tree and generate a new `package-lock.json` file.

CVE-2021-39134 Affected @npmcli/arborist Versions

1 component(s)
Fixed Versions:
2.8.2
Product / Package Ecosystem Affected Versions Fixed Version
@npmcli/arborist
npm
< 2.8.2
2.8.2

References

Frequently Asked Questions

What is CVE-2021-39134?
CVE-2021-39134 is a security vulnerability in @npmcli/arborist involving @npmcli/arborist vulnerable to UNIX Symbolic Link (Symlink) Following under CWE-59: Improper Link Resolution Before File Access ('Link Following').
Which @npmcli/arborist versions are affected?
Affected versions include releases prior to 2.8.2 across affected packages: @npmcli/arborist.
What version fixes CVE-2021-39134?
Upgrading to 2.8.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is @npmcli/arborist affected?
Yes, @npmcli/arborist is affected in releases prior to 2.8.2. Upgrade your dependency to 2.8.2 or later.
What is the CVSS score of CVE-2021-39134?
CVE-2021-39134 has a CVSS v3.1 base score of 8.2 (HIGH) with vector string CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N.
What CWE is associated with CVE-2021-39134?
CVE-2021-39134 is classified under CWE-59: Improper Link Resolution Before File Access ('Link Following') (The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource.).
How can I check npm dependencies for CVE-2021-39134?
Run the dependency tree command: 'npm ls @npmcli/arborist'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-2h3h-q99f-3fhc",
  "modified" : "2022-08-15T20:08:31Z",
  "published" : "2021-08-31T16:04:03Z",
  "aliases" : [ "CVE-2021-39134" ],
  "summary" : "@npmcli/arborist vulnerable to UNIX Symbolic Link (Symlink) Following",
  "details" : "### Impact\n\nArbitrary File Creation, Arbitrary File Overwrite, Arbitrary Code Execution\n\n`@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.\n\nThis 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.\n\nWhen multiple dependencies differ only in the case of their name, Arborist's internal data structure saw 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 allowed an attacker to create a situation in which arbitrary contents could be written to any location on the filesystem.\n\nFor example, a package `pwn-a` could define a dependency in their `package.json` file such as `\"foo\": \"file:/some/path\"`.  Another package, `pwn-b` could define a dependency such as `FOO: \"file:foo.tgz\"`.  On case-insensitive file systems, if `pwn-a` was installed, and then `pwn-b` was installed afterwards, the contents of `foo.tgz` would be written to `/some/path`, and any existing contents of `/some/path` would be removed.\n\nAnyone using npm v7.20.6 or earlier on a case-insensitive filesystem is potentially affected.\n\n### Patches\n\n2.8.2 (included in npm v7.20.7 and above)\n\n### Fix and Caveats\n\nThere are two parts to the fix:\n\n1. Immediately prior to extraction, if the target folder is not a directory, it is moved aside.  (If the installation fails, filesystem entries moved aside in this manner are moved back as part of the rollback process.)\n2. The `children` map that represents child nodes in the tree is replaced with a case-insensitive map object, such that `node.children.get('foo')` and `node.children.get('FOO')` will return the same object, enabling Arborist to detect and handle this class of tree collision.\n\nThis second item imposes a caveat on case _sensitive_ filesystems where two packages with names which differ only in case may already exist at the same level in the tree, causing unpredictable behavior in this rare edge case.  Note that in such cases, the `package-lock.json` already creates a situation which is hazardous to use on case-sensitive filesystems, and will likely lead to other problems.\n\nIf affected by this caveat, please run `npm update` to rebuild your tree and generate a new `package-lock.json` file.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@npmcli/arborist"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.8.2"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/npm/arborist/security/advisories/GHSA-2h3h-q99f-3fhc"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2021-39134"
  }, {
    "type" : "WEB",
    "url" : "https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/npm/arborist"
  }, {
    "type" : "WEB",
    "url" : "https://www.npmjs.com/package/@npmcli/arborist"
  }, {
    "type" : "WEB",
    "url" : "https://www.oracle.com/security-alerts/cpuoct2021.html"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-178", "CWE-59", "CWE-61" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2021-08-31T16:02:46Z",
    "nvd_published_at" : "2021-08-31T17:15:00Z"
  }
}