chore(deps): update dependency next to v14 [security] #5377
+47
−60
Conversation
This file contains 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
zemnmez-renovate-bot
force-pushed
the
renovate/npm-next-vulnerability
branch
28 times, most recently
from
e3fc156
to
51547c1
Compare
zemnmez-renovate-bot
force-pushed
the
renovate/npm-next-vulnerability
branch
28 times, most recently
from
5570dc8
to
a9a71e2
Compare
zemnmez-renovate-bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
a9a71e2
to
faf1d93
Compare
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.
This PR contains the following updates:
13.4.10->14.1.1Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
GitHub Vulnerability Alerts
CVE-2023-46298
Next.js before 13.4.20-canary.13 lacks a cache-control header and thus empty prefetch responses may sometimes be cached by a CDN, causing a denial of service to all users requesting the same URL via that CDN. Cloudflare considers these requests cacheable assets.
CVE-2024-34350
Impact
Inconsistent interpretation of a crafted HTTP request meant that requests are treated as both a single request, and two separate requests by Next.js, leading to desynchronized responses. This led to a response queue poisoning vulnerability in the affected Next.js versions.
For a request to be exploitable, the affected route also had to be making use of the rewrites feature in Next.js.
Patches
The vulnerability is resolved in Next.js
13.5.1and newer. This includes Next.js14.x.Workarounds
There are no official workarounds for this vulnerability. We recommend that you upgrade to a safe version.
References
https://portswigger.net/web-security/request-smuggling/advanced/response-queue-poisoning
CVE-2024-34351
Impact
A Server-Side Request Forgery (SSRF) vulnerability was identified in Next.js Server Actions by security researchers at Assetnote. If the
Hostheader is modified, and the below conditions are also met, an attacker may be able to make requests that appear to be originating from the Next.js application server itself.Prerequisites
<14.1.1) is running in a self-hosted* manner./.* Many hosting providers (including Vercel) route requests based on the Host header, so we do not believe that this vulnerability affects any Next.js applications where routing is done in this manner.
Patches
This vulnerability was patched in #62561 and fixed in Next.js
14.1.1.Workarounds
There are no official workarounds for this vulnerability. We recommend upgrading to Next.js
14.1.1.Credit
Vercel and the Next.js team thank Assetnote for responsibly disclosing this issue to us, and for working with us to verify the fix. Thanks to:
Adam Kues - Assetnote
Shubham Shah - Assetnote
CVE-2024-47831
Impact
The image optimization feature of Next.js contained a vulnerability which allowed for a potential Denial of Service (DoS) condition which could lead to excessive CPU consumption.
Not affected:
next.config.jsfile is configured withimages.unoptimizedset totrueorimages.loaderset to a non-default value.Patches
This issue was fully patched in Next.js
14.2.7. We recommend that users upgrade to at least this version.Workarounds
Ensure that the
next.config.jsfile has eitherimages.unoptimized,images.loaderorimages.loaderFileassigned.Credits
Brandon Dahler (brandondahler), AWS
Dimitrios Vlastaras
CVE-2024-39693
Impact
A Denial of Service (DoS) condition was identified in Next.js. Exploitation of the bug can trigger a crash, affecting the availability of the server.
This vulnerability can affect all Next.js deployments on the affected versions.
Patches
This vulnerability was resolved in Next.js 13.5 and later. We recommend that users upgrade to a safe version.
Workarounds
There are no official workarounds for this vulnerability.
Credit
Release Notes
vercel/next.js (next)
v14.1.1Compare Source
Note: this is a backport release for critical bug fixes -- this does not include all pending features/changes on canary
Core Changes
Credits
Huge thanks to @huozhi, @shuding, @Ethan-Arrowood, @styfle, @ijjk, @ztanner, @balazsorban44, @kdy1, and @williamli for helping!
v14.1.0Compare Source
Core Changes
swc_coretov0.86.98and turbopack: #59393optimize_server_reacttransform: #59390defaulthandling in route groups that handle interception: #59752auto-cjspass: #60118@vercel/[email protected]: #60172<Script>withbeforeInteractivestrategy ignores additional attributes in App Router: #59779auto-cjspass: #60216generateStaticParamswithoutput:export: #57053node-web-audio-apito server-external-packages.json: #60243next dev --experimental-https: #603570cdfef1tof1039be: #60368watchpackto the precompile: #60309chalk: #60317updatedModulesfor App Router and Turbopack changes: #59785RootLayoutwith parallel routes: #60401unstable_cacheimplementation: #60403experimental.missingSuspenseWithCSRBailoutflag: #57642experimental.missingSuspenseWithCSRBailoutflag": #60508f1039beto60a927d: #60619experimental.missingSuspenseWithCSRBailoutflag" (#60508): #60751unstable_getImgProps()=>getImageProps(): #60739normalize-catchall-routestest case: #60777next/headers: #60817browserslistandcaniuse-lite: #60827generateStaticParamswithoutput:export": #60831Documentation Changes
getServerSidePropspage: #59545generateSitemaps: #59626@next/third-partiesdocumentation for Google Analytics: #59671typesafe-i18nfrom thrid-party i18n options: #59624cwdto VSCode debugging setup steps: #58689useFormState: #60010redirectwith client components: #60056maxDurationinfo: #60086⌘+Enterfor forms: #60090Optimizing: Third Party Libraries: #60136revalidatePath'spathhas dynamic segment path,typemust bepage.: #59149Optimizing: Third Party Librarieson tracking pageviews for Google Analytics: #60176revalidatetype annotation: #60230compressiondocs: #60264useSearchParamsbehavior: #60257compress: #60268searchParamsis not passed to Layouts: #60277remotePatternsto mention what happens when prop is omitted: #60387@next/third-partiesbeing experimental: #60372windowHistorySupportflag, and addpushState/replaceStateexamples: #60374windowHistorySupporttitle: #60503.svgunoptimized behavior: #60735Example Changes
with-vitestexample. Unlocks the tests passing withserver-onlyusage: #58902with-algolia-react-instantsearchexample to latest major version and use app router: #59961image-componentexample to App Router: #60289cache-handler-redisexample dependencies: #59458useOptimistic: #60596Misc Changes
swc_coretov0.87.10: #59834swc_coretov0.87.16: #60192create-next-appeven smaller and faster: #58030Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot.