π¨ [security] Update all of nextjs 15.1.5 β 15.3.1 (minor) #162
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
Review or Edit in CodeSandboxOpen the branch in Web Editor β’ VS Code β’ Insiders |
Contributor
Reviewer's Guide by SourceryThis pull request updates Next.js and related dependencies to address known security vulnerabilities. The update includes changes to next, @next/eslint-plugin-next, various @img/sharp-* and @img/sharp-libvips-* packages, and @emnapi/runtime. These updates are crucial for maintaining the application's security posture. Sequence diagram for Authorization Bypass in Next.js MiddlewaresequenceDiagram
participant User
participant Browser
participant Next.js Middleware
participant Backend Server
User->>Browser: Makes a request
Browser->>Next.js Middleware: Request with x-middleware-subrequest header
alt Vulnerable Next.js version
Next.js Middleware->>Backend Server: Bypasses authorization check
Backend Server-->>Next.js Middleware: Returns data
Next.js Middleware-->>Browser: Returns data
else Fixed Next.js version
Next.js Middleware->>Next.js Middleware: Performs authorization check
alt Authorization fails
Next.js Middleware-->>Browser: Returns error
else Authorization succeeds
Next.js Middleware->>Backend Server: Request with authorization
Backend Server-->>Next.js Middleware: Returns data
Next.js Middleware-->>Browser: Returns data
end
end
File-Level Changes
Possibly linked issues
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
Author
|
Closed in favor of #170. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
π¨ 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 update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
β³οΈ @βnext/eslint-plugin-next (15.1.5 β 15.3.1)
Sorry, we couldn't find anything useful about this release.
β³οΈ next (15.1.5 β 15.3.1) Β· Repo
Security Advisories π¨
π¨ Next.js may leak x-middleware-subrequest-id to external hosts
π¨ Authorization Bypass in Next.js Middleware
Release Notes
15.3.1
15.3.0
15.2.5
15.2.4
15.2.3
15.2.2
15.2.1
15.2.0
15.1.7
15.1.6
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
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
Summary by Sourcery
Update Next.js and related dependencies to address security vulnerabilities
New Features:
Bug Fixes: