Skip to content

chore(deps): update dependency undici@<5.29.0 to v7 [security]#121

Closed
renovate[bot] wants to merge 1 commit intodevfrom
renovate/npm-undici<5.29.0-vulnerability
Closed

chore(deps): update dependency undici@&lt;5.29.0 to v7 [security]#121
renovate[bot] wants to merge 1 commit intodevfrom
renovate/npm-undici<5.29.0-vulnerability

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jun 20, 2025

Coming soon: The Renovate bot (GitHub App) will be renamed to Mend. PRs from Renovate will soon appear from 'Mend'. Learn more here.

This PR contains the following updates:

Package Change Age Confidence
undici@<5.29.0 (source) >=5.29.0 -> >=7.16.0 age confidence

GitHub Vulnerability Alerts

CVE-2023-45143

Impact

Undici clears Authorization headers on cross-origin redirects, but does not clear Cookie headers. By design, cookie headers are forbidden request headers, disallowing them to be set in RequestInit.headers in 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-Authorization headers.

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 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

CVE-2024-30260

Impact

Undici cleared Authorization and Proxy-Authorization headers for fetch(), but did not clear them for undici.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 disable maxRedirections.

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-2022-31150

Impact

It is possible to inject CRLF sequences into request headers in Undici.

const undici = require('undici')

const response = undici.request("http://127.0.0.1:1000", {
  headers: {'a': "\r\nb"}
})

The same applies to path and method

Patches

Update to v5.8.0

Workarounds

Sanitize all HTTP headers from untrusted sources to eliminate \r\n.

References

https://hackerone.com/reports/409943
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12116

For more information

If you have any questions or comments about this advisory:

CVE-2022-31151

Impact

Authorization headers are already cleared on cross-origin redirect in
https://github.com/nodejs/undici/blob/main/lib/handler/redirect.js#L189, based on https://github.com/nodejs/undici/issues/872.

However, cookie headers which are sensitive headers and are official headers found in the spec, remain uncleared. There also has been active discussion of implementing a cookie store https://github.com/nodejs/undici/pull/1441, which suggests that there are active users using cookie headers in undici.
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 v5.8.0.

Workarounds

By default, this vulnerability is not exploitable.
Do not enable redirections, i.e. maxRedirections: 0 (the default).

References

https://hackerone.com/reports/1635514
https://curl.se/docs/CVE-2018-1000007.html
https://curl.se/docs/CVE-2022-27776.html

For more information

If you have any questions or comments about this advisory:

CVE-2022-35949

Impact

undici is vulnerable to SSRF (Server-side Request Forgery) when an application takes in user input into the path/pathname option of undici.request.

If a user specifies a URL such as http://127.0.0.1 or //127.0.0.1

const undici = require("undici")
undici.request({origin: "http://example.com", pathname: "//127.0.0.1"})

Instead of processing the request as http://example.org//127.0.0.1 (or http://example.org/http://127.0.0.1 when http://127.0.0.1 is used), it actually processes the request as http://127.0.0.1/ and sends it to http://127.0.0.1.

If a developer passes in user input into path parameter of undici.request, it can result in an SSRF as they will assume that the hostname cannot change, when in actual fact it can change because the specified path parameter is combined with the base URL.

Patches

This issue was fixed in undici@5.8.1.

Workarounds

The best workaround is to validate user input before passing it to the undici.request call.

For more information

If you have any questions or comments about this advisory:

CVE-2022-35948

Impact

=< undici@5.8.0 users are vulnerable to CRLF Injection on headers when using unsanitized input as request headers, more specifically, inside the content-type header.

Example:

import { request } from 'undici'

const unsanitizedContentTypeInput =  'application/json\r\n\r\nGET /foo2 HTTP/1.1'

await request('http://localhost:3000, {
    method: 'GET',
    headers: {
      'content-type': unsanitizedContentTypeInput
    },
})

The above snippet will perform two requests in a single request API call:

  1. http://localhost:3000/
  2. http://localhost:3000/foo2

Patches

This issue was patched in Undici v5.8.1

Workarounds

Sanitize input when sending content-type headers using user input.

For more information

If you have any questions or comments about this advisory:

CVE-2023-23936

Impact

undici library does not protect host HTTP header from CRLF injection vulnerabilities.

Patches

This issue was patched in Undici v5.19.1.

Workarounds

Sanitize the headers.host string 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() and Headers.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 the headerValueNormalize() 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-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@<5.29.0)

v7.16.0

Compare Source

What's Changed

New Contributors

Full Changelog: nodejs/undici@v7.15.0...v7.16.0

v7.15.0

Compare Source

What's Changed

New Contributors

Full Changelog: nodejs/undici@v7.14.0...v7.15.0

v7.14.0

Compare Source

What's Changed

New Contributors

Full Changelog: nodejs/undici@v7.13.0...v7.14.0

v7.13.0

Compare Source

What's Changed

New Contributors

Full Changelog: nodejs/undici@v7.12.0...v7.13.0

v7.12.0

Compare Source

What's Changed

New Contributors

Full Changelog: nodejs/undici@v7.11.0...v7.12.0

v7.11.0

Compare Source

What's Changed

New Contributors

Full Changelog: nodejs/undici@v7.10.0...v7.11.0

v7.10.0

Compare Source

What's Changed

New Contributors

Full Changelog: nodejs/undici@v7.9.0...v7.10.0

v7.9.0

Compare Source

What's Changed

New Contributors

Full Changelog: nodejs/undici@v7.8.0...v7.9.0

v7.8.0

Compare Source

What's Changed

New Contributors

Full Changelog: nodejs/undici@v7.7.0...v7.8.0

v7.7.0

Compare Source

What's Changed


Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from Dougley as a code owner June 20, 2025 12:08
@renovate renovate bot force-pushed the renovate/npm-undici<5.29.0-vulnerability branch from bec59ab to 659178b Compare June 20, 2025 12:16
@renovate renovate bot changed the title chore(deps): update dependency undici@&lt;5.29.0 to v6 [security] chore(deps): update dependency undici@&lt;5.29.0 to v7 [security] Jun 20, 2025
@renovate renovate bot force-pushed the renovate/npm-undici<5.29.0-vulnerability branch from 659178b to c5aaa06 Compare June 20, 2025 16:56
@renovate renovate bot changed the title chore(deps): update dependency undici@&lt;5.29.0 to v7 [security] chore(deps): update dependency undici@&lt;5.29.0 to v6 [security] Jun 20, 2025
@renovate renovate bot force-pushed the renovate/npm-undici<5.29.0-vulnerability branch from c5aaa06 to d011ce5 Compare June 22, 2025 14:32
@renovate renovate bot changed the title chore(deps): update dependency undici@&lt;5.29.0 to v6 [security] chore(deps): update dependency undici@&lt;5.29.0 to v7 [security] Jun 22, 2025
@renovate renovate bot force-pushed the renovate/npm-undici<5.29.0-vulnerability branch from d011ce5 to 692bfe2 Compare June 22, 2025 19:04
@renovate renovate bot changed the title chore(deps): update dependency undici@&lt;5.29.0 to v7 [security] chore(deps): update dependency undici@&lt;5.29.0 to v6 [security] Jun 22, 2025
@renovate renovate bot force-pushed the renovate/npm-undici<5.29.0-vulnerability branch from 692bfe2 to 13f4bcf Compare July 2, 2025 17:19
@renovate renovate bot changed the title chore(deps): update dependency undici@&lt;5.29.0 to v6 [security] chore(deps): update dependency undici@&lt;5.29.0 to v7 [security] Jul 2, 2025
@renovate renovate bot force-pushed the renovate/npm-undici<5.29.0-vulnerability branch from 13f4bcf to 9da710e Compare July 3, 2025 01:47
@renovate renovate bot changed the title chore(deps): update dependency undici@&lt;5.29.0 to v7 [security] chore(deps): update dependency undici@&lt;5.29.0 to v6 [security] Jul 3, 2025
@renovate renovate bot force-pushed the renovate/npm-undici<5.29.0-vulnerability branch from 9da710e to f8a94b3 Compare July 3, 2025 12:36
@renovate renovate bot changed the title chore(deps): update dependency undici@&lt;5.29.0 to v6 [security] chore(deps): update dependency undici@&lt;5.29.0 to v7 [security] Jul 3, 2025
@renovate renovate bot force-pushed the renovate/npm-undici<5.29.0-vulnerability branch 2 times, most recently from 329c73b to 17da810 Compare July 3, 2025 23:55
@renovate renovate bot changed the title chore(deps): update dependency undici@&lt;5.29.0 to v7 [security] chore(deps): update dependency undici@&lt;5.29.0 to v6 [security] Jul 3, 2025
@renovate renovate bot force-pushed the renovate/npm-undici<5.29.0-vulnerability branch from 17da810 to e397f94 Compare July 28, 2025 13:17
@renovate renovate bot changed the title chore(deps): update dependency undici@&lt;5.29.0 to v6 [security] chore(deps): update dependency undici@&lt;5.29.0 to v7 [security] Jul 28, 2025
@renovate renovate bot force-pushed the renovate/npm-undici<5.29.0-vulnerability branch from e397f94 to 155d997 Compare July 28, 2025 20:37
@renovate renovate bot changed the title chore(deps): update dependency undici@&lt;5.29.0 to v7 [security] chore(deps): update dependency undici@&lt;5.29.0 to v6 [security] Jul 28, 2025
@renovate renovate bot force-pushed the renovate/npm-undici<5.29.0-vulnerability branch from 155d997 to cbf38cd Compare August 10, 2025 13:31
@renovate renovate bot changed the title chore(deps): update dependency undici@&lt;5.29.0 to v6 [security] chore(deps): update dependency undici@&lt;5.29.0 to v7 [security] Aug 10, 2025
@renovate renovate bot force-pushed the renovate/npm-undici<5.29.0-vulnerability branch from cbf38cd to 615ddfb Compare August 10, 2025 16:51
@renovate renovate bot changed the title chore(deps): update dependency undici@&lt;5.29.0 to v7 [security] chore(deps): update dependency undici@&lt;5.29.0 to v6 [security] Aug 10, 2025
@renovate renovate bot force-pushed the renovate/npm-undici<5.29.0-vulnerability branch from 615ddfb to 5dbd5c8 Compare August 13, 2025 14:32
@renovate renovate bot changed the title chore(deps): update dependency undici@&lt;5.29.0 to v6 [security] chore(deps): update dependency undici@&lt;5.29.0 to v7 [security] Aug 13, 2025
@renovate renovate bot force-pushed the renovate/npm-undici<5.29.0-vulnerability branch from 5dbd5c8 to 0169796 Compare August 13, 2025 18:09
@renovate renovate bot changed the title chore(deps): update dependency undici@&lt;5.29.0 to v7 [security] chore(deps): update dependency undici@&lt;5.29.0 to v6 [security] Aug 13, 2025
@renovate renovate bot force-pushed the renovate/npm-undici<5.29.0-vulnerability branch from 0169796 to 9fb4bf6 Compare August 19, 2025 19:51
@renovate renovate bot changed the title chore(deps): update dependency undici@&lt;5.29.0 to v6 [security] chore(deps): update dependency undici@&lt;5.29.0 to v7 [security] Aug 19, 2025
@renovate renovate bot force-pushed the renovate/npm-undici<5.29.0-vulnerability branch from 9fb4bf6 to 9f6aa76 Compare August 20, 2025 00:34
@renovate renovate bot changed the title chore(deps): update dependency undici@&lt;5.29.0 to v7 [security] chore(deps): update dependency undici@&lt;5.29.0 to v6 [security] Aug 20, 2025
@renovate renovate bot force-pushed the renovate/npm-undici<5.29.0-vulnerability branch from 9f6aa76 to e3dfe3c Compare August 31, 2025 13:57
@renovate renovate bot changed the title chore(deps): update dependency undici@&lt;5.29.0 to v6 [security] chore(deps): update dependency undici@&lt;5.29.0 to v7 [security] Aug 31, 2025
@renovate renovate bot force-pushed the renovate/npm-undici<5.29.0-vulnerability branch from e3dfe3c to 368c8d3 Compare August 31, 2025 16:32
@renovate renovate bot changed the title chore(deps): update dependency undici@&lt;5.29.0 to v7 [security] chore(deps): update dependency undici@&lt;5.29.0 to v6 [security] Aug 31, 2025
@renovate renovate bot force-pushed the renovate/npm-undici<5.29.0-vulnerability branch from 368c8d3 to 9af63c6 Compare September 25, 2025 20:39
@renovate renovate bot changed the title chore(deps): update dependency undici@&lt;5.29.0 to v6 [security] chore(deps): update dependency undici@&lt;5.29.0 to v7 [security] Sep 25, 2025
@renovate renovate bot force-pushed the renovate/npm-undici<5.29.0-vulnerability branch from 9af63c6 to b3b71f4 Compare September 26, 2025 02:14
@renovate renovate bot changed the title chore(deps): update dependency undici@&lt;5.29.0 to v7 [security] chore(deps): update dependency undici@&lt;5.29.0 to v6 [security] Sep 26, 2025
@renovate renovate bot force-pushed the renovate/npm-undici<5.29.0-vulnerability branch from b3b71f4 to d1947ec Compare September 27, 2025 10:52
@renovate renovate bot changed the title chore(deps): update dependency undici@&lt;5.29.0 to v6 [security] chore(deps): update dependency undici@&lt;5.29.0 to v7 [security] Sep 27, 2025
@renovate renovate bot force-pushed the renovate/npm-undici<5.29.0-vulnerability branch 2 times, most recently from 8757a3f to 6febfeb Compare September 28, 2025 01:45
@renovate renovate bot changed the title chore(deps): update dependency undici@&lt;5.29.0 to v7 [security] chore(deps): update dependency undici@&lt;5.29.0 to v6 [security] Sep 28, 2025
@renovate renovate bot force-pushed the renovate/npm-undici<5.29.0-vulnerability branch from 6febfeb to 792e710 Compare September 28, 2025 01:54
@renovate renovate bot changed the title chore(deps): update dependency undici@&lt;5.29.0 to v6 [security] chore(deps): update dependency undici@&lt;5.29.0 to v7 [security] Sep 28, 2025
@renovate renovate bot force-pushed the renovate/npm-undici<5.29.0-vulnerability branch from 792e710 to cd6a854 Compare September 28, 2025 05:54
@renovate renovate bot changed the title chore(deps): update dependency undici@&lt;5.29.0 to v7 [security] chore(deps): update dependency undici@&lt;5.29.0 to v6 [security] Sep 28, 2025
@Dougley Dougley closed this Sep 28, 2025
@renovate renovate bot changed the title chore(deps): update dependency undici@&lt;5.29.0 to v6 [security] chore(deps): update dependency undici@&lt;5.29.0 to v7 [security] Sep 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant