From cd15caa846ca23c85a0e4aa8f0edae4ed6ad428f Mon Sep 17 00:00:00 2001 From: "depfu[bot]" <23717796+depfu[bot]@users.noreply.github.com> Date: Mon, 6 Jan 2025 10:23:13 +0000 Subject: [PATCH] =?UTF-8?q?=F0=9F=9A=A8=20[security]=20Update=20all=20of?= =?UTF-8?q?=20nextjs=2015.1.0=20=E2=86=92=2015.1.3=20(patch)=20(#15535)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit
Impact
A Denial of Service (DoS) attack allows attackers to construct requests that leaves requests to Server Actions hanging until the hosting provider cancels the function execution.
Note: Next.js server is idle during that time and only keeps the connection open. CPU and memory footprint are low during that time.
Deployments without any protection against long running Server Action invocations are especially vulnerable. Hosting providers like Vercel or Netlify set a default maximum duration on function execution to reduce the risk of excessive billing.
This is the same issue as if the incoming HTTP request has an invalid
Content-Lengthheader or never closes. If the host has no other mitigations to those then this vulnerability is novel.This vulnerability affects only Next.js deployments using Server Actions.
Patches
This vulnerability was resolved in Next.js 14.2.21, 15.1.2, and 13.5.8. We recommend that users upgrade to a safe version.
Workarounds
There are no official workarounds for this vulnerability.
Credits
Thanks to the PackDraw team for responsibly disclosing this vulnerability.
Note
This release is backporting bug fixes. It does not include all pending features/changes on canary.
Core Changes
- Retry manifest file loading only in dev mode: #73900
- Use shared worker for lint & typecheck steps: #74154
Credits
Huge thanks to @unstubbable and @ztanner for helping!
Note
This release is backporting bug fixes. It does not include all pending features/changes on canary.
Core Changes
- Update React from 7283a213-20241206 to 65e06cb7-20241218: #74117
Credits
Huge thanks to @ztanner for helping!
Note
This release is backporting bug fixes. It does not include all pending features/changes on canary.
Core Changes
- fix(turbo): sassOptions silenceDeprecations was not overwritten with user options: #73937
- refactor collectAppPageSegments: #73908
Credits
Huge thanks to @devjiwonchoi and @ztanner for helping!
Does any of this look wrong? Please let us know.
See the full diff on Github. The new version differs by 11 commits:
v15.1.3Backport
v15: used shared worker for lint & typecheck steps (#74154)
(#74285)Backport
v15: Retry manifest file loading only in dev mode (#73900)
(#74283)v15.1.2Backport
(v15): Update React from 7283a213-20241206 to 65e06cb7-20241218
(#74117)v15.1.1run
build_and_test workflow on backport branchbackport:
fix(turbo): sassOptions silenceDeprecations was not overwritten with
user options (#74005)Add
NEXT_PRIVATE_SKIP_CANARY_CHECK env for bench job
(#73763)backport:
refactor collectAppPageSegments (#73996)Designate
as backport branch
- @depfu rebase
- Rebases against your default branch and redoes this update
- @depfu recreate
- Recreates this PR, overwriting any edits that you've made to it
- @depfu merge
- Merges this PR once your tests are passing and conflicts are resolved
- @depfu cancel merge
- Cancels automatic merging of this PR
- @depfu close
- Closes this PR and deletes the branch
- @depfu reopen
- Restores the branch and reopens this PR (if it's closed)
- @depfu pause
- Ignores all future updates for this dependency and closes this PR
- @depfu pause [minor|major]
- Ignores all future minor/major updates for this dependency and closes this PR
- @depfu resume
- Future versions of this dependency will create PRs again (leaves this PR as is)