CVE-2024-37890 Affecting argo-workflows package, versions <3.6.5-r2


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.04% (16th 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-CHAINGUARDLATEST-ARGOWORKFLOWS-9509130
  • published21 Mar 2025
  • disclosed17 Jun 2024

Introduced: 17 Jun 2024

CVE-2024-37890  (opens in a new tab)

How to fix?

Upgrade Chainguard argo-workflows to version 3.6.5-r2 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream argo-workflows package and not the argo-workflows package as distributed by Chainguard. See How to fix? for Chainguard 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 Base Scores

version 3.1