chore(deps): update dependency undici to v5.29.0 [security] #327
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
5.12.0->5.29.0GitHub Vulnerability Alerts
CVE-2023-23936
Impact
undici library does not protect
hostHTTP header from CRLF injection vulnerabilities.Patches
This issue was patched in Undici v5.19.1.
Workarounds
Sanitize the
headers.hoststring before passing to undici.References
Reported at https://hackerone.com/reports/1820955.
Credits
Thank you to Zhipeng Zhang (@timon8) for reporting this vulnerability.
CVE-2023-24807
Impact
The
Headers.set()andHeaders.append()methods are vulnerable to Regular Expression Denial of Service (ReDoS) attacks when untrusted values are passed into the functions. This is due to the inefficient regular expression used to normalize the values in theheaderValueNormalize()utility function.Patches
This vulnerability was patched in v5.19.1.
Workarounds
There is no workaround. Please update to an unaffected version.
References
Credits
Carter Snook reported this vulnerability.
CVE-2023-45143
Impact
Undici clears Authorization headers on cross-origin redirects, but does not clear
Cookieheaders. By design,cookieheaders are forbidden request headers, disallowing them to be set inRequestInit.headersin browser environments. Since Undici handles headers more liberally than the specification, there was a disconnect from the assumptions the spec made, and Undici's implementation of fetch.As such this may lead to accidental leakage of cookie to a 3rd-party site or a malicious attacker who can control the redirection target (ie. an open redirector) to leak the cookie to the 3rd party site.
Patches
This was patched in e041de359221ebeae04c469e8aff4145764e6d76, which is included in version 5.26.2.
CVE-2024-24758
Impact
Undici already cleared Authorization headers on cross-origin redirects, but did not clear
Proxy-Authorizationheaders.Patches
This is patched in v5.28.3 and v6.6.1
Workarounds
There are no known workarounds.
References
CVE-2024-30261
Impact
If an attacker can alter the
integrityoption passed tofetch(), they can letfetch()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
integritycannot be tampered with.References
https://hackerone.com/reports/2377760
CVE-2024-30260
Impact
Undici cleared Authorization and Proxy-Authorization headers for
fetch(), but did not clear them forundici.request().Patches
This has been patched in nodejs/undici@6805746.
Fixes has been released in v5.28.4 and v6.11.1.
Workarounds
use
fetch()or disablemaxRedirections.References
Linzi Shang reported this.
CVE-2025-22150
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
CVE-2025-47279
Impact
Applications that use undici to implement a webhook-like system are vulnerable. If the attacker set up a server with an invalid certificate, and they can force the application to call the webhook repeatedly, then they can cause a memory leak.
Patches
This has been patched in https://github.com/nodejs/undici/pull/4088.
Workarounds
If a webhook fails, avoid keep calling it repeatedly.
References
Reported as: https://github.com/nodejs/undici/issues/3895
Release Notes
nodejs/undici (undici)
v5.29.0Compare Source
What's Changed
Full Changelog: nodejs/undici@v5.28.5...v5.29.0
v5.28.5Compare Source
Fixes CVE CVE-2025-22150 GHSA-c76h-2ccp-4975 (embargoed until 22-01-2025).
Full Changelog: nodejs/undici@v5.28.4...v5.28.5
v5.28.4Compare Source
Full Changelog: nodejs/undici@v5.28.3...v5.28.4
v5.28.3Compare Source
Fixes:
Full Changelog: nodejs/undici@v5.28.2...v5.28.3
v5.28.2Compare Source
What's Changed
node:prefix by @tsctx in #2471nulltype tosignalinRequestInitby @gebsh in #2455New Contributors
Full Changelog: nodejs/undici@v5.28.1...v5.28.2
v5.28.1Compare Source
What's Changed
normalizeMethodby @tsctx in #2456Full Changelog: nodejs/undici@v5.28.0...v5.28.1
v5.28.0Compare Source
What's Changed
substringinstead ofsubstrby @tsctx in #2411Headers#setcorrectly by @tsctx in #2432Headers#deletecorrectly by @tsctx in #2430onHeaderstype declaration by @tsctx in #2444pathmatching inintercept()by @oliversalzburg in #2426New Contributors
Full Changelog: nodejs/undici@v5.27.2...v5.28.0
v5.27.2Compare Source
Full Changelog: nodejs/undici@v5.27.1...v5.27.2
v5.27.1Compare Source
What's Changed
New Contributors
Full Changelog: nodejs/undici@v5.27.0...v5.27.1
v5.27.0Compare Source
What's Changed
Full Changelog: nodejs/undici@v5.26.5...v5.27.0
v5.26.5Compare Source
What's Changed
Full Changelog: nodejs/undici@v5.26.4...v5.26.5
v5.26.4Compare Source
What's Changed
New Contributors
Full Changelog: nodejs/undici@v5.26.3...v5.26.4
v5.26.3Compare Source
v5.26.2Compare Source
Security Release, CVE-2023-45143.
v5.26.1Compare Source
What's Changed
Full Changelog: nodejs/undici@v5.26.0...v5.26.1
v5.26.0Compare Source
What's Changed
nodeby @Ethan-Arrowood in #2310--max-http-header-sizeNode.js flag by @balazsorban44 in #2234New Contributors
Full Changelog: nodejs/undici@v5.23.4...v5.26.0
v5.25.4Compare Source
v5.25.3Compare Source
What's Changed
New Contributors
Full Changelog: nodejs/undici@v5.25.2...v5.25.3
v5.25.2Compare Source
What's Changed
New Contributors
Full Changelog: nodejs/undici@v5.25.1...v5.25.2
v5.25.1Compare Source
What's Changed
Full Changelog: nodejs/undici@v5.25.0...v5.25.1
v5.25.0Compare Source
What's Changed
New Contributors
Full Changelog: nodejs/undici@v5.24.0...v5.25.0
v5.24.0Compare Source
Notable Changes
What's Changed
New Contributors
Full Changelog: nodejs/undici@v5.23.0...v5.24.0
v5.23.0Compare Source
What's Changed
autoselectfamilyon platforms without IPv6 support by @LiviaMedeiros in #2197addAbortListenerwhere applicable by @atlowChemi in #2195New Contributors
Full Changelog: nodejs/undici@v5.22.1...v5.23.0
v5.22.1Compare Source
What's Changed
New Contributors
Full Changelog: nodejs/undici@v5.22.0...v5.22.1
v5.22.0Compare Source
What's Changed
Full Changelog: nodejs/undici@v5.21.2...v5.22.0
v5.21.2Compare Source
What's Changed
Full Changelog: nodejs/undici@v5.21.1...v5.21.2
v5.21.1Compare Source
What's Changed
undefinederror cause by @aduh95 in #2006Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.