fix(deps): update dependency next to v13.5.0 [security] #518
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
renovate
bot
changed the title
Contributor
Author
Autoclosing SkippedThis 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. |
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
2 times, most recently
from
f750de3 to
37084e6
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
37084e6 to
6d23584
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
6d23584 to
a4b701b
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
2 times, most recently
from
6209adb to
2b984f2
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
2b984f2 to
3ed30fc
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
3ed30fc to
32e89e0
Compare
renovate
bot
changed the title
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.1→13.5.0GitHub 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
Release Notes
vercel/next.js (next)
v13.5.0Compare Source
v13.4.19Compare Source
Core Changes
@headlessui/react: #54206devPageFilescollection: #54224RouteandLinkPropsstub generics: #54226createClientModuleProxyfrom Flight Server: #54232loaderFilewhenloader: default: #53417Misc Changes
upgrading.mdxlink : #54234[email protected]: #54246Credits
Huge thanks to @opnay, @styfle, @timneutkens, @ztanner, @shuding, @huozhi, @vinaykulk621, @balazsorban44, @goguda, and @coreyleelarson for helping!
v13.4.18Compare Source
Core Changes
positionindev-build-watcher: #54124sizeproperty toReadonlySearchParams: #53144Misc Changes
Credits
Huge thanks to @huozhi, @shuding, @styfle, @jridgewell, @bencmbrook, @cramforce, and @ztanner for helping!
v13.4.17Compare Source
Core Changes
as anytype cast: #54074fs.promises.rm(): #54076[email protected]: #54125NextRequest: #54108handle_issuesfrom turbopack: #52972cookies().has()breaks in app-route: #54112Documentation Changes
'in data-fetching/fetching-caching-and-revalidating: #54058Example Changes
Misc Changes
swc_coretov0.79.59: #54082packageManagerfield: #54132Credits
Huge thanks to @balazsorban44, @huozhi, @ztanner, @williamli, @wbinnssmith, @kwonoj, @stefanprobst, @feugy, @timneutkens, @kdy1, @Kikobeats, @styfle, @dvoytenko, @MaxLeiter, and @devjiwonchoi for helping!
v13.4.16Compare Source
Core Changes
Documentation Changes
Misc Changes
Credits
Huge thanks to @ijjk, @ztanner, @huozhi, @lacymorrow, @dvoytenko, @kylemcd, @kwonoj, @tibi1220, @wbinnssmith, and @shuding for helping!
v13.4.15Compare Source
Core Changes
changeFrequencyandpriorityattributes to sitemaps: #48484getStaticPaths()for windows: #53876@heroicons/reacttomodularizeImports: #5390218.3.0-canary-1a001dac6-20230812: #53881next-server: #53131Documentation Changes
next/linkanduseRouter.: #53804bunpackage manager: #53590Example Changes
Misc Changes
@next/third-partiespackage: #53996swc_coretov0.79.55: #53831Credits
Huge thanks to @iamarpitpatidar, @pythagoras-yamamoto, @alexkirsz, @sokra, @jsteele-stripe, @tknickman, @gaojude, @styfle, @janicklas-ralph, @huozhi, @ijjk, @vinaykulk621, @balazsorban44, @ztanner, @timneutkens, @ericfennis, @JohnAdib, @MiLk, @kwonoj, @delbaoliveira, @leerob, @LuudJanssen, @lucasconstantino, @davecarlson, @colinhacks, @shuding, @jridgewell, @jantimon, @Banbarashik, @ForsakenHarmony, @kdy1, @dvoytenko, @arturbien, @gnoff, @hsrvms, and @DuCanhGH, @tim-hanssen, @Aryan9592, and @rishabhpoddar for helping!
v13.4.13Compare Source
Core Changes
Next-Urlto http vary in consideration of intercept routes.: #52746yarn add sharptonpm i sharp: #53130Requestcloning viaNextRequest: #53157Documentation Changes
08-parallel-routes.mdx: #53069useRef(): #53015FormDatatype onformDatadefined in.jsfile: #53014Example Changes
Misc Changes
validate-docs-linksrequired: #53123Credits
Huge thanks to @vinaykulk621, @Lantianyou, @styfle, @shuding, @joulev, @AkifumiSato, @trigaten, @HurSungYun, @DevLab2425, @sokra, @alexkirsz, @ztanner, @leerob, @SukkaW, @kwonoj, @huozhi, @ijjk, @balazsorban44, @daniel-web-developer, @ky1ejs, and @arturbien for helping!
v13.4.12Compare Source
Core Changes
Documentation Changes
Misc Changes
swc_coretov0.79.22: #52945Credits
Huge thanks to @ijjk, @wyattjoh, @sokra, @kdy1, @alexkirsz, @styfle, @ShaunFerris, @syedtaqi95, @Heidar-An, @huozhi, and @ztanner for helping!
v13.4.11Compare Source
Core Changes
<preload>fornext/imagein App Router: #52425.txt: #52640moduleResolutionintsconfig.jsonfromnodetobundler: #51957Documentation Changes
jsversion forgenerateMetadata.: #52763Example Changes
force-dynamicfrom all dynamic routes: #52916Misc Changes
Credits
Huge thanks to @styfle, @huozhi, @balazsorban44, @kwonoj, @alexkirsz, @ijjk, @Jeffrey-Zutt, @timneutkens, @vinaykulk621, @Ryan-Dia, @sokra, @shuding, @steppefox, @hiro0218, @rjsdnql123, @feedthejim, @fgiuliani, @steven-tey, @AntoineBourin, @adamrhunter, @darshanjain-entrepreneur, @s0h311, @wyattjoh, @ztanner, @djreillo, @dijonmusters, and @cassidoo for helping!
v13.4.10Compare Source
Core Changes
get_client_chunking_contextindependent of context: #51928ensurePagerequests for the same page: #52360output: "standalone"crashing build when there is noapp/page: #51993serverComponentsExternalPackages: #52388next-types-pluginforNode16/NodeNext: #52562[email protected]: #52649Documentation Changes
useSearchParams: #52348create-next-apprequires public GitHub URLs.: #52367fetchrequest de-duplication: #52100next/image: #52480formDataexample for Route Handlers: #52358metadataobject: #52252_appand_document: #52479Example Changes
0.19): #52473Misc Changes
v0.79.13: #52371not-found.tsxwithoutput: export: #52526npm packinstead ofyarn pack: #52563body-parser: #52580Credits
Huge thanks to @ijjk, @anonrig, @alexkirsz, @gfgabrielfranca, @styfle, @ztanner, @leerob, @sokra, @huozhi, @Bitbbot, @wyattjoh, @kdy1, @wbinnssmith, @shuding, @jridgewell, @BrennanColberg, @Nick-Mazuk, @delbaoliveira, @thomasballinger, @lucgagan, @nroland013, @SonMooSans, @jenewland1999, @thorwebdev, @jyunhanlin, @darshanjain-entrepreneur, @DuCanhGH, @Gnadhi, @yagogmaisp, @carlos-menezes, @balazsorban44, @ryo-manba, @timneutkens, @feedthejim, @vamcs, @matepapp, @SleeplessOne1917, @ecklf, @djreillo, @kwonoj, @gnoff, @feugy, @karlhorky, @starunaway, @FernandVEYRIER, [@Ryan-Di
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 this update again.
This PR was generated by Mend Renovate. View the repository job log.