Use of Insufficiently Random Values Affecting jitsucom-jitsu package, versions <2.8.6-r1


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.04% (13th 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 Learn

Learn about Use of Insufficiently Random Values vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-CHAINGUARDLATEST-JITSUCOMJITSU-8661283
  • published24 Jan 2025
  • disclosed21 Jan 2025

Introduced: 21 Jan 2025

CVE-2025-22150  (opens in a new tab)
CWE-330  (opens in a new tab)

How to fix?

Upgrade Chainguard jitsucom-jitsu to version 2.8.6-r1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream jitsucom-jitsu package and not the jitsucom-jitsu package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

Undici is an HTTP/1.1 client. Starting in version 4.5.0 and prior to versions 5.28.5, 6.21.1, and 7.2.3, undici uses Math.random() to choose the boundary for a multipart/form-data request. It is known that the output of Math.random() can be predicted if several of its generated values are known. If there is a mechanism in an app that sends multipart requests to an attacker-controlled website, they can use this to leak the necessary values. Therefore, an attacker can tamper with the requests going to the backend APIs if certain conditions are met. This is fixed in versions 5.28.5, 6.21.1, and 7.2.3. As a workaround, do not issue multipart requests to attacker controlled servers.

CVSS Base Scores

version 3.1