Denial of service when handling a request with many HTTP headers in ws
websockets ws
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| ws npm |
|
|
websockets ws
| Product | Affected | Fixed in |
|---|---|---|
| ws npm |
|
|
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.
From the CVE record · GitHub_M
Vulnerable versions of the Node.js ws package can crash when a request contains more headers than server.maxHeadersCount allows. An attacker who can send such a request to a ws server can cause the crash; the input does not specify authentication requirements.
Check servers using npm ws versions >=2.1.0 <5.2.4, >=6.0.0 <6.2.3, >=7.0.0 <7.5.10, or >=8.0.0 <8.17.1.