-
Notifications
You must be signed in to change notification settings - Fork 0
fix(deps): update dependency next to v11 [security] #359
base: master
Are you sure you want to change the base?
Conversation
2d772f9 to
5346a9b
Compare
WalkthroughThis update involves a significant upgrade of the Next.js framework from version 9.5.5 to 11.1.3 in the project's Changes
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files ignored due to path filters (1)
app/yarn.lockis excluded by!**/yarn.lock,!**/*.lock
Files selected for processing (1)
- app/package.json (1 hunks)
Additional comments not posted (1)
app/package.json (1)
21-21: Major version upgrade of Next.js from 9.5.5 to 11.1.3.This significant upgrade may introduce breaking changes and new features. Ensure that the application is tested thoroughly to verify compatibility with the new version. Check the release notes for any breaking changes and update the codebase accordingly.
a8e3dec to
5346a9b
Compare
This PR contains the following updates:
9.5.5->11.1.3GitHub Vulnerability Alerts
CVE-2021-43803
Next.js is a React framework. In versions of Next.js prior to 12.0.5 or 11.1.3, invalid or malformed URLs could lead to a server crash. In order to be affected by this issue, the deployment must use Next.js versions above 11.1.0 and below 12.0.5, Node.js above 15.0.0, and next start or a custom server. Deployments on Vercel are not affected, along with similar environments where invalid requests are filtered before reaching Next.js. Versions 12.0.5 and 11.1.3 contain patches for this issue. Note that prior version 0.9.9 package
nexthosted a different utility (0.4.1 being the latest version of that codebase), and this advisory does not apply to those versions.CVE-2021-37699
Next.js is an open source website development framework to be used with the React library. In affected versions 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 it can allow for phishing attacks by redirecting to an attacker's domain from a trusted domain.Impact
10.0.5and10.2.011.0.0and11.0.1usingpages/_error.jswithoutgetInitialProps11.0.0and11.0.1usingpages/_error.jsandnext exportpages/404.jsnextnpm package hosted a different utility (0.4.1 being the latest version of that codebase), and this advisory does not apply to those versions.We recommend upgrading to the latest version of Next.js to improve the overall security of your application.
Patches
https://github.com/vercel/next.js/releases/tag/v11.1.0
Release Notes
vercel/next.js (next)
v11.1.3Compare Source
See https://github.com/vercel/next.js/releases/v12.0.5 for details about this patch.
v11.1.2Compare Source
Core Changes
Credits
Huge thanks to @huozhi and @kara for helping!
v11.1.1Compare Source
Core Changes
NextConfigtype: #27974generateBuildIdtype that can be async function: #28040Documentin preparation for streaming: #28032utilto 0.12.4: #27939next-env.d.tson read-only filesystems: #28206next/image: #28221zen-observablelibrary: #28214next/imageblur placeholder when JS is disabled: #28269process.exittonext lintsuccess output: #28299typescriptproperty toNextConfig: #28459next/image: #28517Documentation Changes
next/imagedocs around layouts.: #28345sharpusage to mention Vercel: #28476Example Changes
private: true: #28008.gitignoreto examples that lack them: #28003licencefrom allexample/package.jsonthat has them: #28007with-couchbaseexample: #27184create-next-app: #28431Misc Changes
no-import-document-in-pagerule: #28261Credits
Huge thanks to @delbaoliveira, @padmaia, @andersonleite, @stefanprobst, @oBusk, @sokra, @xnuk, @styfle, @leerob, @devknoll, @huozhi, @timneutkens, @awareness481, @agektmr, @gu-stav, @sampoder, @Thisen, @ijjk, @oscarafuentes, @AryanBeezadhur, @bmuenzenmeyer, @tdkn, @rgabs, @urko-pineda, @davecaruso, @kevinold, @ctjlewis, @chrislloyd, @mrmckeb, @housseindjirdeh, @hiro0218, @Bezmehrabi, @atcastle, @janicklas-ralph, @lorensr, @lekterable, @vcnc-hex, @ejscribner, @Andarist, @aravindputrevu, @robbieaverill, @zhafri-shafiq, @htunnicliff, @kukicado, @OzzieOrca, @mikehedman, and @kmelve for helping!
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
security@vercel.com. 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](https:/
Configuration
📅 Schedule: Branch creation - "" in timezone Asia/Tokyo, 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.