🚨 [security] [site] Update all of nextjs 13.0.0 → 16.2.3 (major)#11
Open
depfu[bot] wants to merge 1 commit into1.1from
Open
🚨 [security] [site] Update all of nextjs 13.0.0 → 16.2.3 (major)#11depfu[bot] wants to merge 1 commit into1.1from
depfu[bot] wants to merge 1 commit into1.1from
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
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.
Welcome to Depfu 👋
This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.
After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.
Let us know if you have any questions. Thanks so much for giving Depfu a try!
🚨 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?
✳️ eslint-config-next (13.0.0 → 16.2.3)
Sorry, we couldn't find anything useful about this release.
✳️ next (13.0.0 → 16.2.3) · Repo
Security Advisories 🚨
🚨 Next.js has a Denial of Service with Server Components
🚨 Next.js has a Denial of Service with Server Components
🚨 Next.js: HTTP request smuggling in rewrites
🚨 Next.js: HTTP request smuggling in rewrites
🚨 Next.js: Unbounded next/image disk cache growth can exhaust storage
🚨 Next.js: Unbounded postponed resume buffering can lead to DoS
🚨 Next.js: null origin can bypass Server Actions CSRF checks
🚨 Next.js: null origin can bypass dev HMR websocket CSRF checks
🚨 Next.js: Unbounded next/image disk cache growth can exhaust storage
🚨 Next.js HTTP request deserialization can lead to DoS when using insecure React Server Components
🚨 Next.js has Unbounded Memory Consumption via PPR Resume Endpoint
🚨 Next.js has Unbounded Memory Consumption via PPR Resume Endpoint
🚨 Next.js HTTP request deserialization can lead to DoS when using insecure React Server Components
🚨 Next.js HTTP request deserialization can lead to DoS when using insecure React Server Components
🚨 Next.js HTTP request deserialization can lead to DoS when using insecure React Server Components
🚨 Next.js HTTP request deserialization can lead to DoS when using insecure React Server Components
🚨 Next.js HTTP request deserialization can lead to DoS when using insecure React Server Components
🚨 Next.js HTTP request deserialization can lead to DoS when using insecure React Server Components
🚨 Next.js HTTP request deserialization can lead to DoS when using insecure React Server Components
🚨 Next.js HTTP request deserialization can lead to DoS when using insecure React Server Components
🚨 Next.js self-hosted applications vulnerable to DoS via Image Optimizer remotePatterns configuration
🚨 Next.js self-hosted applications vulnerable to DoS via Image Optimizer remotePatterns configuration
🚨 Next has a Denial of Service with Server Components - Incomplete Fix Follow-Up
🚨 Next has a Denial of Service with Server Components - Incomplete Fix Follow-Up
🚨 Next has a Denial of Service with Server Components - Incomplete Fix Follow-Up
🚨 Next has a Denial of Service with Server Components - Incomplete Fix Follow-Up
🚨 Next has a Denial of Service with Server Components - Incomplete Fix Follow-Up
🚨 Next has a Denial of Service with Server Components - Incomplete Fix Follow-Up
🚨 Next has a Denial of Service with Server Components - Incomplete Fix Follow-Up
🚨 Next has a Denial of Service with Server Components - Incomplete Fix Follow-Up
🚨 Next has a Denial of Service with Server Components - Incomplete Fix Follow-Up
🚨 Next Server Actions Source Code Exposure
🚨 Next Vulnerable to Denial of Service with Server Components
🚨 Next Vulnerable to Denial of Service with Server Components
🚨 Next Vulnerable to Denial of Service with Server Components
🚨 Next Vulnerable to Denial of Service with Server Components
🚨 Next Vulnerable to Denial of Service with Server Components
🚨 Next Vulnerable to Denial of Service with Server Components
🚨 Next Vulnerable to Denial of Service with Server Components
🚨 Next Vulnerable to Denial of Service with Server Components
🚨 Next Vulnerable to Denial of Service with Server Components
🚨 Next Server Actions Source Code Exposure
🚨 Next Server Actions Source Code Exposure
🚨 Next Server Actions Source Code Exposure
🚨 Next Server Actions Source Code Exposure
🚨 Next Server Actions Source Code Exposure
🚨 Next Server Actions Source Code Exposure
🚨 Next Server Actions Source Code Exposure
🚨 Next.js is vulnerable to RCE in React flight protocol
🚨 Next.js is vulnerable to RCE in React flight protocol
🚨 Next.js is vulnerable to RCE in React flight protocol
🚨 Next.js is vulnerable to RCE in React flight protocol
🚨 Next.js is vulnerable to RCE in React flight protocol
🚨 Next.js is vulnerable to RCE in React flight protocol
🚨 Next.js is vulnerable to RCE in React flight protocol
🚨 Next.js Content Injection Vulnerability for Image Optimization
🚨 Next.js Content Injection Vulnerability for Image Optimization
🚨 Next.js Affected by Cache Key Confusion for Image Optimization API Routes
🚨 Next.js Improper Middleware Redirect Handling Leads to SSRF
🚨 Next.js Improper Middleware Redirect Handling Leads to SSRF
🚨 Next.JS vulnerability can lead to DoS via cache poisoning
🚨 Next.js has a Cache poisoning vulnerability due to omission of the Vary header
🚨 Information exposure in Next.js dev server due to lack of origin verification
🚨 Information exposure in Next.js dev server due to lack of origin verification
🚨 Next.js Race Condition to Cache Poisoning
🚨 Next.js Race Condition to Cache Poisoning
🚨 Next.js may leak x-middleware-subrequest-id to external hosts
🚨 Next.js may leak x-middleware-subrequest-id to external hosts
🚨 Next.js may leak x-middleware-subrequest-id to external hosts
🚨 Authorization Bypass in Next.js Middleware
🚨 Authorization Bypass in Next.js Middleware
🚨 Authorization Bypass in Next.js Middleware
🚨 Next.js Allows a Denial of Service (DoS) with Server Actions
🚨 Next.js Allows a Denial of Service (DoS) with Server Actions
🚨 Next.js Allows a Denial of Service (DoS) with Server Actions
🚨 Next.js authorization bypass vulnerability
🚨 Denial of Service condition in Next.js image optimization
🚨 Next.js Cache Poisoning
🚨 Next.js Cache Poisoning
🚨 Next.js Denial of Service (DoS) condition
🚨 Next.js Vulnerable to HTTP Request Smuggling
🚨 Next.js Server-Side Request Forgery in Server Actions
🚨 Next.js missing cache-control header may lead to CDN caching empty reply
Release Notes
Too many releases to show here. View the full release notes.
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