NULL Pointer Dereference Affecting rh-dotnet60-dotnet-runtime-6.0 package, versions *


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.04% (15th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL7-RHDOTNET60DOTNETRUNTIME60-7276679
  • published19 Jun 2024
  • disclosed16 Jun 2024

Introduced: 16 Jun 2024

CVE-2024-37890  (opens in a new tab)
CWE-476  (opens in a new tab)
CWE-400  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:7 rh-dotnet60-dotnet-runtime-6.0.

NVD Description

Note: Versions mentioned in the description apply only to the upstream rh-dotnet60-dotnet-runtime-6.0 package and not the rh-dotnet60-dotnet-runtime-6.0 package as distributed by RHEL. See How to fix? for RHEL:7 relevant fixed versions and status.

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.

CVSS Scores

version 3.1