temporalio/temporal-ecommerce

babel-eslint-10.1.0.tgz: 1 vulnerabilities (highest severity is: 7.5) - autoclosed

Closed this issue · 1 comments

Vulnerable Library - babel-eslint-10.1.0.tgz

Path to dependency file: /frontend/package.json

Path to vulnerable library: /frontend/node_modules/path-parse/package.json

Found in HEAD commit: 91f5d7a169fd359bad9e33b954d19e6f8f7adac5

Vulnerabilities

CVE Severity CVSS Dependency Type Fixed in Remediation Available
CVE-2021-23343 High 7.5 path-parse-1.0.6.tgz Transitive 11.0.0-beta.0

Details

CVE-2021-23343

Vulnerable Library - path-parse-1.0.6.tgz

Node.js path.parse() ponyfill

Library home page: https://registry.npmjs.org/path-parse/-/path-parse-1.0.6.tgz

Path to dependency file: /frontend/package.json

Path to vulnerable library: /frontend/node_modules/path-parse/package.json

Dependency Hierarchy:

  • babel-eslint-10.1.0.tgz (Root Library)
    • resolve-1.20.0.tgz
      • path-parse-1.0.6.tgz (Vulnerable Library)

Found in HEAD commit: 91f5d7a169fd359bad9e33b954d19e6f8f7adac5

Found in base branch: main

Vulnerability Details

All versions of package path-parse are vulnerable to Regular Expression Denial of Service (ReDoS) via splitDeviceRe, splitTailRe, and splitPathRe regular expressions. ReDoS exhibits polynomial worst-case time complexity.

Publish Date: 2021-05-04

URL: CVE-2021-23343

CVSS 3 Score Details (7.5)

Base Score Metrics:

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

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: jbgutierrez/path-parse#8

Release Date: 2021-05-04

Fix Resolution (path-parse): 1.0.7

Direct dependency fix Resolution (babel-eslint): 11.0.0-beta.0

⛑️ Automatic Remediation is available for this issue


⛑️ Automatic Remediation is available for this issue.

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