loftwah/casualcoder.io

CVE-2021-23343 (High) detected in path-parse-1.0.6.tgz - autoclosed

Closed this issue · 2 comments

CVE-2021-23343 - High Severity Vulnerability

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: /wp-content/themes/twentytwenty/package.json

Path to vulnerable library: /wp-content/themes/twentytwenty/node_modules/path-parse/package.json,/wp-content/themes/twentynineteen/node_modules/path-parse/package.json,/wp-content/themes/twentytwentyone/node_modules/path-parse/package.json

Dependency Hierarchy:

  • node-sass-6.0.0.tgz (Root Library)
    • meow-3.7.0.tgz
      • normalize-package-data-2.5.0.tgz
        • resolve-1.11.1.tgz
          • path-parse-1.0.6.tgz (Vulnerable Library)

Found in HEAD commit: 14ae92bd92b84f61737b3ee22fa2cc32e9fbdf03

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 (node-sass): 6.0.1


Step up your Open Source Security Game with WhiteSource here

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

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