chore(deps): bump undici from 7.25.0 to 7.29.0 in /examples/with-mtls - #2792
Conversation
Bumps [undici](https://github.com/nodejs/undici) from 7.25.0 to 7.29.0. - [Release notes](https://github.com/nodejs/undici/releases) - [Commits](nodejs/undici@v7.25.0...v7.29.0) --- updated-dependencies: - dependency-name: undici dependency-version: 7.29.0 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
| next@15.5.15: | ||
| resolution: {integrity: sha512-VSqCrJwtLVGwAVE0Sb/yikrQfkwkZW9p+lL/J4+xe+G3ZA+QnWPqgcfH1tDUEuk9y+pthzzVFp4L/U8JerMfMQ==} | ||
| engines: {node: ^18.18.0 || ^19.8.0 || >= 20.0.0} | ||
| next@16.2.9: |
There was a problem hiding this comment.
Risk: Affected versions of next are vulnerable to Server-Side Request Forgery (SSRF). This Next.js config defines a rewrites()/redirects() rule whose destination builds an external hostname from a dynamic :param segment. Because the segment is not constrained to hostname-safe characters, an attacker can inject a value (e.g. containing a dot) that escapes the intended hostname suffix, causing Next.js to proxy the request server-side to an arbitrary host (SSRF) or redirect the client to an attacker-controlled destination (open redirect). Constrain each dynamic segment used in a destination hostname to hostname-safe characters (e.g. [a-z0-9-]+), or upgrade Next.js.
Manual Review Advice: A vulnerability from this advisory is reachable if you define a rewrites() or redirects() rule in next.config.js whose destination hostname is assembled from a dynamic :param segment
Fix: Upgrade this library to at least version 16.2.11 at nextjs-auth0/examples/with-mtls/pnpm-lock.yaml:311.
Reference(s): GHSA-p9j2-gv94-2wf4
🌟 Fixed in commit 5341d2f 🌟
| next@15.5.15: | ||
| resolution: {integrity: sha512-VSqCrJwtLVGwAVE0Sb/yikrQfkwkZW9p+lL/J4+xe+G3ZA+QnWPqgcfH1tDUEuk9y+pthzzVFp4L/U8JerMfMQ==} | ||
| engines: {node: ^18.18.0 || ^19.8.0 || >= 20.0.0} | ||
| next@16.2.9: |
There was a problem hiding this comment.
Risk: Affected versions of next are vulnerable to Excessive Iteration. Next.js App Router validates multi-page-application (MPA) form submissions by iterating over every $ACTION_REF_-prefixed form field without an upper bound, decoding a bound-argument descriptor for each one. An attacker can POST a form containing a large number of these fields, forcing excessive CPU usage that blocks processing of further requests in the same process, resulting in a denial of service. Declaring any Server Action ("use server") registers it in the server module map and arms this handler.
Manual Review Advice: A vulnerability from this advisory is reachable if you are using the App Router with at least one Server Action
Fix: Upgrade this library to at least version 16.2.11 at nextjs-auth0/examples/with-mtls/pnpm-lock.yaml:311.
Reference(s): GHSA-m99w-x7hq-7vfj
🎈 Fixed in commit 5341d2f 🎈
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2792 +/- ##
=======================================
Coverage 87.98% 87.98%
=======================================
Files 80 80
Lines 11514 11514
Branches 2385 2385
=======================================
Hits 10131 10131
Misses 1338 1338
Partials 45 45 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Bumps undici from 7.25.0 to 7.29.0.
Release notes
Sourced from undici's releases.
... (truncated)
Commits
9e38fc1Bumped v7.29.0 (#5590)d887e34fix: validate coerced header values for CRLF (#5579)33928bcfix: validate blob body content type98011a8fix(cache): harden cache directive parsing4a9dafbtest(retry): correct broken content-range fixtures in retry-handler.js1b5a531fix(retry): reject partial content length mismatch466e99dtest: cover crash on mixed unqualified and qualified private cache directives9f10f1efix: handle empty qualified private cache directive3bf91ddfix: harden cookie domain, path, and unparsed attribute validationf9eba0aBumped v7.28.0 (#5430)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.