fix(deps): update dependency next to v11 [security] - autoclosed #32
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:
6.1.1->11.1.0GitHub Vulnerability Alerts
CVE-2021-37699
Impact
10.0.5and10.2.011.0.0and11.0.1usingpages/_error.jswithoutgetInitialProps11.0.0and11.0.1usingpages/_error.jsandnext exportpages/404.jsWe recommend everyone to upgrade regardless of whether you can reproduce the issue or not.
Patches
https://github.com/vercel/next.js/releases/tag/v11.1.0
Release Notes
vercel/next.js
v11.1.0Compare Source
A security team from one of our partners noticed an issue in Next.js that allowed for an open redirect to occur.
Specially encoded paths could be used when
pages/_error.jswas statically generated allowing an open redirect to occur to an external site.In general, this redirect does not directly harm users although can allow for phishing attacks by redirecting to an attacker's domain from a trusted domain.
We recommend upgrading to the latest version of Next.js to improve the overall security of your application.
How to Upgrade
npm install next@latest --saveImpact
pages/_error.jswithoutgetInitialPropspages/_error.jsandnext exportpages/404.jsWe recommend everyone to upgrade regardless of whether you can reproduce the issue or not.
How to Assess Impact
If you think sensitive code or data could have been exposed, you can filter logs of affected sites by
//(double slash at the start of the url) followed by a domain.What is Being Done
As Next.js has grown in popularity and usage by enterprises, it has received the attention of security researchers and auditors. We are thankful to Gabriel Benmergui from Robinhood for their investigation and discovery of the original bug and subsequent responsible disclosure.
We've landed a patch that ensures path parsing is handled properly for these paths so that the open redirect can no longer occur.
Regression tests for this attack were added to the security integration test suite
[email protected]. We are actively monitoring this mailbox.Release notes
Core Changes
next lint: #26697next-dev-serverimplementation: #26230max-ageto optimized image: #26739onLoadingComplete()prop to Image component: #26824.eslintrcfile created to have.jsonformat: #26884ResponsePayloadsupport: #26938IncrementalCacheAPI: #26941respondWith: #26961next/scriptinterface Props to ScriptProps: #26990next/imageTS types forwidthandheight: #26991dangerously-unoptimizedloader for next/image: #26847next/imageTS types forsrc: #26996dangerously-unoptimizedtocustomand warn when applicable: #26998next-env.d.ts: #27028next devperformance with placeholder=blur: #27061web-vitalsto v1.1.2.: #25272withCoalescedInvokewithResponseCache: #26997minimumCacheTTLconfig for Image Optimization: #27200next/scriptcomponent: #27218minimumCacheTTLso it doesn't affect browser caching: #27307placeholder=blurinside<noscript>: #27311RequestContext: #27303keepAlivetonode-fetchpolyfill: #27376nullresponses: #27403lazyBoundaryprop to Image component: #27258NextConfigtype: #27446next/imagecomponent hasstyleprop: #27441--formatflag tonext lint: #27052RenderResult: #27319onLoadingComplete()callback: #27695next.config.jsoption to override defaultkeepAlive: #27709removeHeader()function to image optimizer mock res: #27763next lintis run for the first time: #26584elseto fix tree shaking: #27788placeholderwithblurDataURLin globalStaticImageDatatype: #27916next/scriptunhandled promise rejection: #27903concurrentFeaturesconfig: #27768next buildwhen sharp is missing: #27933Documentation Changes
no-duplicate-headrule: #27179next/imagedocs withonLoadingComplete(): #27440next/scriptmust not be innext/head: #27534Example Changes
lunix→linux: #26796package.json: #27121hrefdid not match error: #27183asprop from<Link>components: #27359utiltolibinwith-mongodbexample: #27404utilstolibinwith-mongodb-mongooseexample: #27407Misc Changes
publish-canaryscript to include checkout: #26840create-next-appnext-env.d.ts: #26890placeholder=blurwithassetPrefix: #27120next/scripttopages/_appin script loader integration tests: #27626next buildwhen sharp is missing (#27933)"Credits
Huge thanks to @atcastle, @vitalybaev, @leerob, @destruc7i0n, @styfle, @petermekhaeil, @phocks, @pranavp10, @huozhi, @ijjk, @johnrackles, @timneutkens, @Vadorequest, @hiro0218, @housseindjirdeh, @sohamsshah, @devknoll, @schoenwaldnils, @kasipavankumar, @jviide, @sedlukha, @PaulvdDool, @padmaia, @LetItRock, @angeloashmore, @sachinraja, @pa-rang, @theostrahlen, @schultzp2020, @lsndr, @sokra, @andys-github, @darshkpatel, @tanys123, @papaponmx, @karlsander, @borekb, @michielvangendt, @rishabhpoddar, @enesakar, @ctbarna, @markkaylor, @stovmascript, @lucleray, @mvasilkov, @nyedidikeke, @mastoj, @janicklas-ralph, @ThangHuuVu, @Munawwar, @reod, @thomasmarshall, @AndreVarandas, @Ryz0nd, @qwertyforce, @samrobbins85, @brandonchinn178, @adam-cowley, @akellbl4, @jflayhart, @jaybekster, @stuymedova, @m-abdelwahab, @UniqueNL, @jamsinclair, @fabb, @abotsi, @kylemh, @JacobLey, @AryanBeezadhur, @afbarbaro, @javivelasco, @breyed, @roim, @mandarons, @stefanprobst, @sa3dany, @jarvelov, @apuyou, @gnbaron, @kaykdm, @michalbundyra, @brijendravarma, @tmcgann, @arturmuller, @noahweingand, @omasher, @yunger7, @raon0211, @noreiller, @shibe23, @enzoferey, @JeffersonBledsoe, @Timvdv, @smitssjors, @zackdotcomputer, @jameshoward, @tigger9flow, @sergioalvz, @tomchen, @kdy1, @zeekrey, @NickKelly1, @orta, @euess, @NickCrews, @ctjlewis, @delbaoliveira, @ahmedosama7450, @samsisle, and @mrmckeb for helping!
v11.0.1Compare Source
Core Changes
--quietflag, TypeScript resolver and bug fixes: #26280Router.events.onandRouter.events.off: #26456Documentation Changes
next/imagedocs version history: #26192--ts, --typescriptfrom Options: #26252next/scriptdocumentation.: #26325Example Changes
future.webpack5-> top levelwebpack5: #26175Misc Changes
passHrefdocs link.: #26402Credits
Huge thanks to @HermanNygaard, @styfle, @IvanKalinin, @lachlanjc, @Braweria, @RileyMShea, @Dev-CasperTheGhost, @CauanCabral, @toyamarinyon, @DavidVaness, @nickbabcock, @jwilsson, @timneutkens, @antoinechalifour, @valse, @arshad, @Silinde87, @Vadorequest, @tim-hanssen, @ducdev, @rishabhpoddar, @LEvinson2504, @akellbl4, @schemburkar, @greatSumini, @giraffesyo, @zNeb, @jthcast, @devknoll, @housseindjirdeh, @lukeingalls, @joe-bell, @leerob, @pacocoursey, @aksdevac, @araujogui, @ijjk, @vitalybaev, @samrobbins85, @huozhi, @petermekhaeil, @RobVermeer, and @flybayer for helping!
v11.0.0Compare Source
Core Changes
react@experimentalifreactRootis set: #25496next lint+ ESLint in Create Next App: #25064^17.0.2: #25788@types/comment-json: #25810placeholder=blur: #25945Configuration
📅 Schedule: "" (UTC).
🚦 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 has been generated by WhiteSource Renovate. View repository job log here.