Skip to content

Undici's fetch with integrity option is too lax when algorithm is specified but hash value is in incorrect

Low severity GitHub Reviewed Published Apr 4, 2024 in nodejs/undici • Updated Apr 29, 2024

Package

npm undici (npm)

Affected versions

< 5.28.4
>= 6.0.0, < 6.11.1

Patched versions

5.28.4
6.11.1

Description

Impact

If an attacker can alter the integrity option passed to fetch(), they can let fetch() accept requests as valid even if they have been tampered.

Patches

Fixed in nodejs/undici@d542b8c.
Fixes has been released in v5.28.4 and v6.11.1.

Workarounds

Ensure that integrity cannot be tampered with.

References

https://hackerone.com/reports/2377760

References

@mcollina mcollina published to nodejs/undici Apr 4, 2024
Published to the GitHub Advisory Database Apr 4, 2024
Reviewed Apr 4, 2024
Published by the National Vulnerability Database Apr 4, 2024
Last updated Apr 29, 2024

Severity

Low

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
Low
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
Low
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:L/UI:R/S:U/C:N/I:L/A:N

EPSS score

0.059%
(27th percentile)

Weaknesses

CVE ID

CVE-2024-30261

GHSA ID

GHSA-9qxr-qj54-h672

Source code

Credits

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