Update dependency next to v12.3.5 [SECURITY] #273
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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
11d4138 to
4a83359
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
4a83359 to
463ab4a
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
463ab4a to
f0f93e7
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
f0f93e7 to
1d6aeda
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:
12.0.7->12.3.5GitHub Vulnerability Alerts
CVE-2022-21721
Impact
Vulnerable code could allow a bad actor to trigger a denial of service attack for anyone running a Next.js app at version >= 12.0.0, and using i18n functionality.
Patches
A patch has been released,
next@12.0.9, that mitigates this issue. We recommend all affected users upgrade as soon as possible.Workarounds
We recommend upgrading whether you can reproduce or not although you can ensure
/${locale}/_next/is blocked from reaching the Next.js instance until you upgrade.For more information
If you have any questions or comments about this advisory:
CVE-2022-23646
Next.js is a React framework. Starting with version 10.0.0 and prior to version 12.1.0, Next.js is vulnerable to User Interface (UI) Misrepresentation of Critical Information. In order to be affected, the
next.config.jsfile must have animages.domainsarray assigned and the image host assigned inimages.domainsmust allow user-provided SVG. If thenext.config.jsfile hasimages.loaderassigned to something other than default, the instance is not affected. Version 12.1.0 contains a patch for this issue. As a workaround, changenext.config.jsto use a differentloader configurationother than the default.Impact
next.config.jsfile has images.domains array assignednext.config.jsfile has images.loader assigned to something other than defaultPatches
Next.js 12.1.0
Workarounds
Change
next.config.jsto use a different loader configuration other than the default, for example:Or if you want to use the
loaderprop on the component, you can usecustom: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-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-51479
Impact
If a Next.js application is performing authorization in middleware based on pathname, it was possible for this authorization to be bypassed.
Patches
This issue was patched in Next.js
14.2.15and later.If your Next.js application is hosted on Vercel, this vulnerability has been automatically mitigated, regardless of Next.js version.
Workarounds
There are no official workarounds for this vulnerability.
Credits
We'd like to thank tyage (GMO CyberSecurity by IERAE) for responsible disclosure of this issue.
CVE-2025-29927
Impact
It is possible to bypass authorization checks within a Next.js application, if the authorization check occurs in middleware.
Patches
15.2.314.2.2513.5.912.3.5Note: 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-subrequestheader from reaching your Next.js application.Credits
Release Notes
vercel/next.js (next)
v12.3.5Compare Source
v12.3.4Compare Source
v12.3.3Compare Source
v12.3.2Compare Source
v12.3.1Compare Source
Core Changes
experimental: { esmExternals: 'loose' }: #40377next/dynamicshould only add default loading without suspense: #40397AppType: #40391onLoadconcurrent rendering resilient: #40191fallbackNodePolyfills: false: #40612notFound: truein/withnext export: #40592CONTRIBUTING.md: #40515Documentation Changes
swcMinify: trueout of "Experimental features" section: #40394loadingproperty: #40488Example Changes
Misc Changes
link:instead offile:in CONTRIBUTING.md: #40510/errors/directory.tar: #40513next/scriptbeforeInteractive test in both dev & prod: #40541Credits
Huge thanks to @huozhi, @shuding, @ijjk, @jasham, @Kikobeats, @wyattjoh, @rubytree33, @timneutkens, @balazsorban44, @andrewrjohn, @SukkaW, @hanneslund, @leerob, @Djo1e, @kdy1, @msafi, @tknickman, @feugy, @cramforce, @ryparker, @victorboucher, @steven-tey, @JDansercoer, @janklimo, @hiro0218, @HaNdTriX, @migueloller, @flex-kyunghwa, @saalimzafar, @alxhotel, @janicklas-ralph, @feedthejim, and @chornos13 for helping!
v12.3.0Compare Source
Core Changes
SPACE_AROUND_COLONregex: #39710fetchresponse: #39608onErrorhandling innext/future/image: #39824next/future/imagewhenobjectFitorobjectPosition: #39614next/future/imageblur-up placeholder : #39785@vercel/nft@0.22.0: #39906AppProps's generic forpageProps: #38867next/future/imageincorrectly warning forfill+blur: #39986experimental.fallbackNodePolyfillsflag: #39248next/scriptin the server build by default: #40013next/future/imageto use svg blur placeholder duringnext dev: #39992<noscript>fromnext/future/image: #40075filePathbeing wrongly stringified: #40070altto required innext/future/image: #40136next devandnext start: #40118next/future/image,remotePatterns,unoptimized: #40142@vercel/nft@0.22.1: #40164next/config: #40224next/future/imageto support onlywidthor onlyheight: #40278RemoveConsole: #40296react/no-unknown-property: #40331onLoadingCompletefornext/future/imageto receive reference to<img>: #40326Documentation Changes
next/future/imagedocs about Known Browser Bugs: #39759exportPathMapwithgetStaticPaths: #39813next/future/imagewith details about computed aspect ratio: #39829largePageDataBytesin warning docs: #39941script.md: #40017pageExtensions: #40016jest.config.js: #40090remotePatternsimage config: #40350Example Changes
hideSourceMaps: #40079image-componentexample types: #40352Misc Changes
npmversion in issue validator: #38915Credits
Huge thanks to @stipsan, @ijjk, @timneutkens, @bennettdams, @shuding, @cherniavskii, @huozhi, @Brooooooklyn, @thatbeautifuldream, @Janpot, @MoosaSaadat, @alexcole, @HaNdTriX, @magic-akari, @balazsorban44, @styfle, @SukkaW, @kdy1, @sokra, @delbaoliveira, @puneetkathar1, @nkzawa, @Schniz, @greebl3, @kasperaamodt, @chaseignited, @masad-frost, @Kikobeats, @davewelsh, @MaedahBatool, @adrianbienias, @michaeloliverx, @arthurdenner, @sumiren, @migueloller, @hanneslund, @wyattjoh, @kwonoj, @boredland, @simongavelin, @esbenam, @theMosaad, @jleclanche, @leerob, @AdilAmanat, @souporserious, @ykdojo, @sanjaiyan-dev, @yoannmoinet, @thomasballinger, @titusdmoore, @jferrettiboke, @Dueen, @dunglas, @KenAKAFrosty, @wbinnssmith, @schehata, @remorses, @visnup, @Nutlope, @yhay81, @hiro0218, @avigoldman, @feugy, @jeferson-sb, @lobsterkatie, @atcastle, @bcheidemann, @Will956, @orionmiz, @S0UPernova, @cvbuelow, and @leonzalion for helping!
v12.2.6Compare Source
v12.2.5Compare Source
Core Changes
next/future/imagealt text: #39366eslint-plugin-eslint-pluginto ensureeslint-plugin-nextrules follow ESLint rule best practices along with enforcing some consistency.: #37920--output-fileflag: #36420Documentation Changes
context.queryingetServerSideProps(): #39422router.prefetchdocumentation to includelocaleoption: #39442Example Changes
Misc Changes
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.