Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependency next to v14.2.21 [SECURITY] - abandoned #3035

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
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.15 -> ^14.2.21 age adoption passing confidence
next (source) 14.2.15 -> 14.2.21 age adoption passing confidence

GitHub Vulnerability Alerts

CVE-2024-51479

Impact

If a Next.js application is performing authorization in middleware based on pathname, it was possible for this authorization to be bypassed.

Patches

This issue was patched in Next.js 14.2.15 and later.

If your Next.js application is hosted on Vercel, this vulnerability has been automatically mitigated, regardless of Next.js version.

Workarounds

There are no official workarounds for this vulnerability.

Credits

We'd like to thank tyage (GMO CyberSecurity by IERAE) for responsible disclosure of this issue.

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

v14.2.20

Compare Source

v14.2.19

Compare Source

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes
  • ensure worker exits bubble to parent process (#​73433)
  • Increase max cache tags to 128 (#​73125)
Misc Changes
  • Update max tag items limit in docs (#​73445)
Credits

Huge thanks to @​ztanner and @​ijjk for helping!

v14.2.18

Compare Source

v14.2.17

Compare Source

v14.2.16

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 becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates 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 added the dependencies label Jan 4, 2025
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from b9274f0 to e526efe Compare January 7, 2025 08:48
@renovate renovate bot changed the title Update dependency next to v14.2.21 [SECURITY] Update dependency next [SECURITY] Jan 7, 2025
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from e526efe to 0acc9bd Compare January 7, 2025 08:51
@renovate renovate bot changed the title Update dependency next [SECURITY] Update dependency next to v14.2.21 [SECURITY] Jan 7, 2025
@johnnyomair johnnyomair self-assigned this Jan 7, 2025
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from 0acc9bd to 2d7f7d2 Compare January 7, 2025 09:08
@renovate renovate bot changed the title Update dependency next to v14.2.21 [SECURITY] Update dependency next [SECURITY] Jan 7, 2025
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from 2d7f7d2 to 4ba07f6 Compare January 7, 2025 09:34
@renovate renovate bot changed the title Update dependency next [SECURITY] Update dependency next to v14.2.21 [SECURITY] Jan 7, 2025
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from 4ba07f6 to afe2141 Compare January 7, 2025 14:57
@renovate renovate bot changed the title Update dependency next to v14.2.21 [SECURITY] Update dependency next [SECURITY] Jan 7, 2025
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from afe2141 to 7dc68be Compare January 7, 2025 15:10
@renovate renovate bot changed the title Update dependency next [SECURITY] Update dependency next to v14.2.21 [SECURITY] Jan 7, 2025
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from 7dc68be to dc3627e Compare January 7, 2025 15:15
@renovate renovate bot changed the title Update dependency next to v14.2.21 [SECURITY] Update dependency next [SECURITY] Jan 7, 2025
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from dc3627e to 22ae867 Compare January 7, 2025 15:19
@renovate renovate bot changed the title Update dependency next [SECURITY] Update dependency next to v14.2.21 [SECURITY] Jan 7, 2025
@renovate renovate bot changed the title Update dependency next to v14.2.21 [SECURITY] Update dependency next to v14.2.21 [SECURITY] - abandoned Jan 7, 2025
Copy link
Contributor Author

renovate bot commented Jan 7, 2025

Autoclosing Skipped

This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.

@johnnyomair johnnyomair closed this Jan 8, 2025
@johnnyomair johnnyomair deleted the renovate/npm-next-vulnerability branch January 8, 2025 16:14
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