Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jan 4, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
next (source) 14.2.20 -> 14.2.21 age adoption passing confidence

GitHub Vulnerability Alerts

CVE-2024-56332

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-Length header 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.


Release Notes

vercel/next.js (next)

v14.2.21

Compare Source


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


  • 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 force-pushed the renovate/npm-next-vulnerability branch from 8d7b578 to 750efdd Compare January 23, 2025 21:51
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from 750efdd to deec31c Compare February 9, 2025 14:26
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from deec31c to 5707fd0 Compare March 3, 2025 15:59
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch 3 times, most recently from ccc72ab to b2f9e2f Compare March 17, 2025 16:56
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from b2f9e2f to 8da285a Compare April 1, 2025 10:25
@ktmouk ktmouk merged commit 2ada94d into main Apr 6, 2025
6 checks passed
@ktmouk ktmouk deleted the renovate/npm-next-vulnerability branch April 6, 2025 08:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants