Skip to content

🚨 [security] Update next 12.1.0 → 12.3.5 (minor) #301

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

depfu[bot]
Copy link
Contributor

@depfu depfu bot commented Mar 24, 2025


🚨 Your current dependencies have known security vulnerabilities 🚨

This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!


Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ next (12.1.0 → 12.3.5) · Repo

Security Advisories 🚨

🚨 Authorization Bypass in Next.js Middleware

Impact

It is possible to bypass authorization checks within a Next.js application, if the authorization check occurs in middleware.

Patches

  • For Next.js 15.x, this issue is fixed in 15.2.3
  • For Next.js 14.x, this issue is fixed in 14.2.25
  • For Next.js 13.x, this issue is fixed in 13.5.9
  • For Next.js 12.x, this issue is fixed in 12.3.5
  • For Next.js 11.x, consult the below workaround.

Note: Next.js deployments hosted on Vercel are automatically protected against this vulnerability.

Workaround

If patching to a safe version is infeasible, it is recommend that you prevent external user requests which contain the x-middleware-subrequest header from reaching your Next.js application.

Credits

  • Allam Rachid (zhero;)
  • Allam Yasser (inzo_)

🚨 Unexpected server crash in Next.js

Impact

When specific requests are made to the Next.js server it can cause an unhandledRejection in the server which can crash the process to exit in specific Node.js versions with strict unhandledRejection handling.

  • Affected: All of the following must be true to be affected by this CVE

    • Node.js version above v15.0.0 being used with strict unhandledRejection exiting
    • Next.js version v12.2.3
    • Using next start or a custom server
  • Not affected: Deployments on Vercel (vercel.com) are not affected along with similar environments where next-server isn't being shared across requests.

Patches

https://github.com/vercel/next.js/releases/tag/v12.2.4

Release Notes

Too many releases to show here. View the full release notes.

Sorry, we couldn't find anything useful about this release.

↗️ @​next/env (indirect, 12.1.0 → 12.3.5) · Repo

Sorry, we couldn't find anything useful about this release.

↗️ styled-jsx (indirect, 5.0.0 → 5.0.7) · Repo · Changelog

Release Notes

5.0.7

5.0.7 (2022-09-09)

Bug Fixes

5.0.6

5.0.6 (2022-09-05)

Bug Fixes

5.0.5

5.0.5 (2022-09-02)

Improvements

Misc

  • Replace bundler #802

5.0.4

5.0.4 (2022-08-11)

Bug Fixes

5.0.3

5.0.3 (2022-08-09)

Patches

  • declare module and fix conflict typing name #805
  • improvement: add typing for style imports #804

Documentation

  • docs: update typescript guide with babel plugin #801
  • chore: remove git.io #794

5.0.2

5.0.2 (2022-03-28)

Performance Improvements

  • including macro.d.ts to decalaration files (#791) (cac4b8c)

5.0.1

5.0.1 (2022-03-13)

Bug Fixes

  • peer dep declaration for react 18 with npm (#788) (384d208)

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 17 commits:

🆕 @​swc/helpers (added, 0.4.11)

🆕 use-sync-external-store (added, 1.2.0)

🗑️ @​next/swc-android-arm64 (removed)

🗑️ @​next/swc-darwin-x64 (removed)

🗑️ @​next/swc-linux-arm64-gnu (removed)

🗑️ @​next/swc-linux-arm64-musl (removed)

🗑️ use-subscription (removed)


Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands
@​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)

@depfu depfu bot added the depfu label Mar 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants