CVE-2019-16776 (High) detected in npm-6.9.0.tgz - autoclosed

[mend-bolt-for-github]

CVE-2019-16776 - High Severity Vulnerability

Vulnerable Library - npm-6.9.0.tgz

a package manager for JavaScript

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

Path to dependency file: stripe-distinct-usage-tracking/package.json

Path to vulnerable library: stripe-distinct-usage-tracking/node_modules/npm

Dependency Hierarchy:

• semantic-release-15.13.18.tgz (Root Library)
  • npm-5.1.7.tgz
    • ❌ npm-6.9.0.tgz (Vulnerable Library)

Found in HEAD commit: 288b1c7d0d0acd2be479cdcac3dd10a64fc6e714

Vulnerability Details

Versions of the npm CLI prior to 6.13.3 are vulnerable to an Arbitrary File Write. It fails to prevent access to folders outside of the intended node_modules folder through the bin field. A properly constructed entry in the package.json bin field would allow a package publisher to modify and/or gain access to arbitrary files on a user's system when the package is installed. This behavior is still possible through install scripts. This vulnerability bypasses a user using the --ignore-scripts install option.

Publish Date: 2019-12-13

URL: CVE-2019-16776

CVSS 3 Score Details (8.1)

Base Score Metrics:

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

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://blog.npmjs.org/post/189618601100/binary-planting-with-the-npm-cli

Release Date: 2019-12-13

Fix Resolution: npm - 6.13.3;yarn - 1.21.1

---

Step up your Open Source Security Game with WhiteSource here

[mend-bolt-for-github]

ℹ️ This issue was automatically closed by WhiteSource because it is a duplicate of an existing issue: #144

[mend-bolt-for-github]

ℹ️ This issue was automatically closed by WhiteSource because it is a duplicate of an existing issue: #144