CVE-2021-43616 (Critical) detected in npm-7.16.0.tgz

[mend-bolt-for-github]

CVE-2021-43616 - Critical Severity Vulnerability

Vulnerable Library - npm-7.16.0.tgz

a package manager for JavaScript

Library home page: https://registry.npmjs.org/npm/-/npm-7.16.0.tgz

Path to dependency file: /package.json

Path to vulnerable library: /node_modules/npm/package.json

Dependency Hierarchy:

• npm-7.1.3.tgz (Root Library)
  • ❌ npm-7.16.0.tgz (Vulnerable Library)

Found in base branch: master

Vulnerability Details

** DISPUTED ** The npm ci command in npm 7.x and 8.x through 8.1.3 proceeds with an installation even if dependency information in package-lock.json differs from package.json. This behavior is inconsistent with the documentation, and makes it easier for attackers to install malware that was supposed to have been blocked by an exact version match requirement in package-lock.json. NOTE: The npm team believes this is not a vulnerability. It would require someone to socially engineer package.json which has different dependencies than package-lock.json. That user would have to have file system or write access to change dependencies. The npm team states preventing malicious actors from socially engineering or gaining file system access is outside the scope of the npm CLI.

Publish Date: 2021-11-13

URL: CVE-2021-43616

CVSS 3 Score Details (9.8)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: High
  • Integrity Impact: High
  • Availability Impact: High

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://nvd.nist.gov/vuln/detail/CVE-2021-43616

Release Date: 2021-11-13

Fix Resolution (npm): 8.1.4

Direct dependency fix Resolution (@semantic-release/npm): 9.0.0

---

Step up your Open Source Security Game with Mend here

[github-actions]

👋 Thanks for reporting!