fix(deps): update dependency next to v11 [security] #442
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
force-pushed
the
renovate/npm-next-vulnerability
branch
from
4c83b74
to
ae590d3
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
7 times, most recently
from
3a43b06
to
b65f0c5
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
2 times, most recently
from
07fc5d3
to
63ae2a3
Compare
renovate
bot
changed the title
renovate
bot
changed the title
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. ⚠ Warning: custom changes will be lost. |
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
4 times, most recently
from
5cfbc16
to
56bcff0
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
56bcff0
to
90e1085
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:
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
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, @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, [@lu
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 has been generated by Mend Renovate. View repository job log here.