CVE Vulnerabilities

CVE-2025-22150

Use of Insufficiently Random Values

Published: Jan 21, 2025 | Modified: Jan 21, 2025
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
RedHat/V2
RedHat/V3
6.8 MODERATE
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N
Ubuntu
MEDIUM

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.

Weakness

The product uses insufficiently random numbers or values in a security context that depends on unpredictable numbers.

Affected Software

Name Vendor Start Version End Version
Red Hat Developer Hub 1.3 on RHEL 9 RedHat rhdh-hub-container-1.3-142 *
Red Hat Enterprise Linux 8 RedHat nodejs:20-8100020250203134842.489197e6 *
Red Hat Enterprise Linux 8 RedHat nodejs:18-8100020250207121904.489197e6 *
Red Hat Enterprise Linux 8 RedHat nodejs:22-8100020250130144944.6d880403 *
Red Hat Enterprise Linux 9 RedHat nodejs:20-9050020250130114516.rhel9 *
Red Hat Enterprise Linux 9 RedHat nodejs:18-9050020250206154514.rhel9 *
Red Hat Enterprise Linux 9 RedHat nodejs:22-9050020250131131518.rhel9 *
Red Hat Developer Hub (RHDH) 1.5 RedHat registry.redhat.io/rhdh/rhdh-hub-rhel9:sha256:56bfbb2328f42e91d0462e142f3434e5d771737defbc07d8a21dbdf50e468665 *
Red Hat OpenShift AI 2.16 RedHat registry.redhat.io/rhoai/odh-dashboard-rhel8:sha256:13da7e12e135cdb33c89686eca84cffae8ef691fcb4f346622ebd9b47f0a69ee *
Red Hat OpenShift AI 2.18 RedHat registry.redhat.io/rhoai/odh-dashboard-rhel8:sha256:31339f9880eb772739b95373c38b3fd556d7c0979b6e794210eee42bbb15759a *
RHDH 1.4 RedHat registry.redhat.io/rhdh/rhdh-hub-rhel9:sha256:5eb109362246ccddd564febe6387bc6015d47555df00c36aa88c2247099851b7 *

Potential Mitigations

  • Use a well-vetted algorithm that is currently considered to be strong by experts in the field, and select well-tested implementations with adequate length seeds.
  • In general, if a pseudo-random number generator is not advertised as being cryptographically secure, then it is probably a statistical PRNG and should not be used in security-sensitive contexts.
  • Pseudo-random number generators can produce predictable numbers if the generator is known and the seed can be guessed. A 256-bit seed is a good starting point for producing a “random enough” number.

References