depcheck-0.6.7.tgz: 1 vulnerabilities (highest severity is: 5.3)

[dev-mend-for-github-com]

Vulnerable Library - depcheck-0.6.7.tgz

Path to dependency file: /package.json

Path to vulnerable library: /node_modules/yargs/node_modules/yargs-parser/package.json

Found in HEAD commit: dc72fe758102dbf0f0ce66aec41bfbe074e87beb

Vulnerabilities

CVE	Severity	CVSS	Dependency	Type	Fixed in (depcheck version)	Remediation Possible**
CVE-2020-7608	Medium	5.3	yargs-parser-4.2.1.tgz	Transitive	0.6.8	✅

**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation

Details

CVE-2020-7608

Vulnerable Library - yargs-parser-4.2.1.tgz

the mighty option parser used by yargs

Library home page: https://registry.npmjs.org/yargs-parser/-/yargs-parser-4.2.1.tgz

Path to dependency file: /package.json

Path to vulnerable library: /node_modules/yargs/node_modules/yargs-parser/package.json

Dependency Hierarchy:

• depcheck-0.6.7.tgz (Root Library)
  • yargs-6.6.0.tgz
    • ❌ yargs-parser-4.2.1.tgz (Vulnerable Library)

Found in HEAD commit: dc72fe758102dbf0f0ce66aec41bfbe074e87beb

Found in base branch: main

Vulnerability Details

yargs-parser could be tricked into adding or modifying properties of Object.prototype using a "proto" payload.

Publish Date: 2020-03-16

URL: CVE-2020-7608

CVSS 3 Score Details (5.3)

Base Score Metrics:

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

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Release Date: 2020-03-16

Fix Resolution (yargs-parser): 5.0.0-security.0

Direct dependency fix Resolution (depcheck): 0.6.8

⛑️ Automatic Remediation will be attempted for this issue.

---

⛑️Automatic Remediation will be attempted for this issue.

[dev-mend-for-github-com]

✔️ This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.

[dev-mend-for-github-com]

ℹ️ This issue was automatically re-opened by Mend because the vulnerable library in the specific branch(es) has been detected in the Mend inventory.