Skip to content

Use of Insufficiently Random Values in undici

Moderate severity GitHub Reviewed Published Jan 21, 2025 in nodejs/undici • Updated Jan 22, 2025

Package

npm undici (npm)

Affected versions

>= 4.5.0, < 5.28.5
>= 6.0.0, < 6.21.1
>= 7.0.0, < 7.2.3

Patched versions

5.28.5
6.21.1
7.2.3

Description

Impact

Undici fetch() 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.

Patches

This is fixed in 5.28.5; 6.21.1; 7.2.3.

Workarounds

Do not issue multipart requests to attacker controlled servers.

References

References

@mcollina mcollina published to nodejs/undici Jan 21, 2025
Published by the National Vulnerability Database Jan 21, 2025
Published to the GitHub Advisory Database Jan 21, 2025
Reviewed Jan 21, 2025
Last updated Jan 22, 2025

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N

Weaknesses

CVE ID

CVE-2025-22150

GHSA ID

GHSA-c76h-2ccp-4975

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.