ws is an open source WebSocket client and server for Node.js. A request with a number of headers exceeding theserver.maxHeadersCount threshold could be used to crash a ws server. The vulnerability was fixed in ws@8.17.1 (e55e510) and backported to ws@7.5.10 (22c2876), ws@6.2.3 (eeb76d3), and ws@5.2.4 (4abd8f6). In vulnerable versions of ws, the issue can be mitigated in the following ways: 1. Reduce the maximum allowed length of the request headers using the --max-http-header-size=size and/or the maxHeaderSize options so that no more headers than the server.maxHeadersCount limit can be sent. 2. Set server.maxHeadersCount to 0 so that no limit is applied.
CVE-2024-37890 - High Severity Vulnerability
Vulnerable Libraries - ws-8.16.0.tgz, ws-8.5.0.tgz, ws-7.4.6.tgz
ws-8.16.0.tgz
Library home page: https://registry.npmjs.org/ws/-/ws-8.16.0.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/web3-providers-ws/node_modules/ws/package.json
Dependency Hierarchy: - web3-4.6.0.tgz (Root Library) - web3-providers-ws-4.0.7.tgz - :x: **ws-8.16.0.tgz** (Vulnerable Library)
ws-8.5.0.tgz
Simple to use, blazing fast and thoroughly tested websocket client and server for Node.js
Library home page: https://registry.npmjs.org/ws/-/ws-8.5.0.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/ws/package.json
Dependency Hierarchy: - ethers-6.11.1.tgz (Root Library) - :x: **ws-8.5.0.tgz** (Vulnerable Library)
ws-7.4.6.tgz
Simple to use, blazing fast and thoroughly tested websocket client and server for Node.js
Library home page: https://registry.npmjs.org/ws/-/ws-7.4.6.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/engine.io/node_modules/ws/package.json
Dependency Hierarchy: - socket.io-3.1.2.tgz (Root Library) - engine.io-4.1.2.tgz - :x: **ws-7.4.6.tgz** (Vulnerable Library)
Found in base branch: master
Vulnerability Details
ws is an open source WebSocket client and server for Node.js. A request with a number of headers exceeding theserver.maxHeadersCount threshold could be used to crash a ws server. The vulnerability was fixed in ws@8.17.1 (e55e510) and backported to ws@7.5.10 (22c2876), ws@6.2.3 (eeb76d3), and ws@5.2.4 (4abd8f6). In vulnerable versions of ws, the issue can be mitigated in the following ways: 1. Reduce the maximum allowed length of the request headers using the --max-http-header-size=size and/or the maxHeaderSize options so that no more headers than the server.maxHeadersCount limit can be sent. 2. Set server.maxHeadersCount to 0 so that no limit is applied.
Publish Date: 2024-06-17
URL: CVE-2024-37890
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/websockets/ws/security/advisories/GHSA-3h5v-q93c-6h6q
Release Date: 2024-06-17
Fix Resolution (ws): 8.17.1
Direct dependency fix Resolution (web3): 4.7.0
Fix Resolution (ws): 8.17.1
Direct dependency fix Resolution (socket.io): 4.0.0