Tim-sandbox / nodegoat

Apache License 2.0
0 stars 1 forks source link

CVE-2020-7662 (High) detected in websocket-extensions-0.1.3.tgz - autoclosed #79

Closed mend-for-github-com[bot] closed 3 years ago

mend-for-github-com[bot] commented 3 years ago

CVE-2020-7662 - High Severity Vulnerability

Vulnerable Library - websocket-extensions-0.1.3.tgz

Generic extension manager for WebSocket connections

Library home page: https://registry.npmjs.org/websocket-extensions/-/websocket-extensions-0.1.3.tgz

Path to dependency file: nodegoat/package.json

Path to vulnerable library: nodegoat/node_modules/websocket-extensions/package.json

Dependency Hierarchy: - grunt-contrib-watch-1.1.0.tgz (Root Library) - tiny-lr-1.1.1.tgz - faye-websocket-0.10.0.tgz - websocket-driver-0.7.0.tgz - :x: **websocket-extensions-0.1.3.tgz** (Vulnerable Library)

Found in HEAD commit: a7cf759168f0c98d6d469e2711fda2875be7080b

Found in base branch: master

Vulnerability Details

websocket-extensions npm module prior to 0.1.4 allows Denial of Service (DoS) via Regex Backtracking. The extension parser may take quadratic time when parsing a header containing an unclosed string parameter value whose content is a repeating two-byte sequence of a backslash and some other character. This could be abused by an attacker to conduct Regex Denial Of Service (ReDoS) on a single-threaded server by providing a malicious payload with the Sec-WebSocket-Extensions header.

Publish Date: 2020-06-02

URL: CVE-2020-7662

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: https://github.com/advisories/GHSA-g78m-2chm-r7qv

Release Date: 2020-06-02

Fix Resolution: websocket-extensions - 0.1.4

mend-for-github-com[bot] commented 3 years ago

:heavy_check_mark: 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.