This repository was archived by the owner on May 28, 2023. It is now read-only.
Update dependency next to v12 [SECURITY]#683
Open
renovate[bot] wants to merge 1 commit intomasterfrom
Open
Conversation
|
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/rshackleton/rshackleton-co-uk/DFcrPCwypDR8jHCe2nVKtS9BNxab |
ca42a87 to
ce265ed
Compare
ce265ed to
9687622
Compare
9687622 to
0a54734
Compare
0a54734 to
6d70fc7
Compare
6d70fc7 to
3442758
Compare
3442758 to
61f8389
Compare
61f8389 to
b4fc80d
Compare
b4fc80d to
6755f02
Compare
6755f02 to
c396754
Compare
c396754 to
bcf45b5
Compare
bcf45b5 to
aa145e7
Compare
aa145e7 to
524dbed
Compare
524dbed to
1e064b6
Compare
1e064b6 to
b52ec4f
Compare
f2c6662 to
add37ad
Compare
add37ad to
0419186
Compare
0419186 to
60951b4
Compare
60951b4 to
d5c6a49
Compare
d5c6a49 to
792f294
Compare
792f294 to
8607039
Compare
8607039 to
eea5224
Compare
eea5224 to
4a16447
Compare
4a16447 to
d9132b8
Compare
d9132b8 to
30dea9a
Compare
30dea9a to
a7694ab
Compare
a7694ab to
cf72c5f
Compare
cf72c5f to
326e769
Compare
326e769 to
79e49f2
Compare
Author
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. |
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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:
10.2.3->12.1.0GitHub Vulnerability Alerts
CVE-2021-39178
Impact
next.config.jsfile hasimages.domainsarray assignedimages.domainsallows user-provided SVGnext.config.jsfile hasimages.loaderassigned to something other than defaultPatches
Next.js v11.1.1
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:Release Notes
vercel/next.js
v12.1.0Compare Source
Core Changes
artifactDirectory: #33918react-dom/server.browserin Node.js: #33950ReadableStreaminRenderResult: #34005Linkto pass event toonClickhandler: #27723lazyRootfunctionality fornext/image: #33933Routerstate immutable: #33925renderandrenderErrormethods fromnext/client: #34069concurrentFeatureswithruntime: #34068renderToStreamwith React 18: #34106next/imageusage fromnode_modules: #33559react-dom/server.browserwhenreactRoot: true: #34116.envfile in standalone mode: #34143next-server.ts: #34230runtimeis set tonodejs: #34228node-sass@7as peer dependency: #34107<RouteAnnouncer/>shouldn't announce initial path under strict mode and React 18: #34338dangerouslyAllowSVGandcontentSecurityPolicy: #34431.svgimage optimization with aloaderprop: #34452Documentation Changes
.endinstead of.sendwhen no body is being sent: #33611profileDatatodatain CSR page: #34018asyncto middleware docs.: #31356urltonextUrlinside delete-query-params-in-middlewa…: #33796fallback: true: #34114invalid-api-status-bodyerror: #34150lazyRootprop: #34241getting started: #34282getInitialProps: #34309Example Changes
yarn lint.: #34019next/imagein the Sanity example: #34203profilein firebase example: #34457Misc Changes
Credits
Huge thanks to @MaedahBatool, @mutebg, @sokra, @huozhi, @hanford, @shuding, @sean6bucks, @jameshfisher, @devknoll, @yuta-ike, @zh-lx, @amandeepmittal, @alunyov, @stefanprobst, @leerob, @balazsorban44, @kdy1, @brittanyrw, @jord1e, @kara, @vvo, @ismaelrumzan, @dlindenkreuz, @MohammadxAli, @nguyenyou, @thibautsabot, @hanneslund, @vertti, @KateKate, @stefee, @mikinovation, @Leticijak, @mohsen1, @ncphillips, @ehowey, @lancechentw, @krychaxp, @fmacherey, @pklawansky, @RyanClementsHax, @lakbychance, @sannajammeh, @oliviertassinari, @alexander-akait, @u-yas, @Cheprer, @msp5382, @chrispat, @getspooky, @Ryz0nd, @klaasman, @midgleyc, @kumard3, @jesstelford, @neeraj3029, @glenngijsberts, @pie6k, @wouterraateland, @timneutkens, @11koukou, @thesyedbasim, @aeneasr, @ijjk, @lfades, @JuniorTour, @xavhan, @mattyocode, @padmaia, @Skn0tt, @gwer, @Nutlope, @styfle, @stipsan, @xhoantran, @eolme, @sespinosa, @zenorocha, @hjaber, @benmvp, @T-O-R-U-S, @dburrows, @atcastle, @kiriny, @molebox, @kitayoshi, and @Schniz for helping!
v12.0.10Compare Source
Core Changes
compressconfigurable in standalone mode: #33717stale-while-revalidatepattern to Image Optimization API: #33735Documentation Changes
Example Changes
with-dockerexample dockerfile: #33695Misc Changes
lock.ymlCredits
Huge thanks to @Vienio99, @balazsorban44, @kyliau, @molebox, @huozhi, @shuding, @PepijnSenders, @krystofex, @PizzaPete, @souljuse, @styfle, @Schniz, @Nelsonfrank, @ijjk, @Mhmdrza, @timneutkens, @hideokamoto-stripe, @Emrin, @gr-qft, @delbaoliveira, @redbar0n, @amandeepmittal, @lxy-yz, and @Divlo for helping!
v12.0.9Compare Source
This upgrade is completely backward-compatible and recommended for all users on versions below 12.0.9
Vulnerable code could allow a bad actor to trigger a denial of service attack via the
/${locale}/_next/route for anyone running a Next.js app at version >= 12.0.0, and using built-in i18n routing functionality.How to Upgrade
npm install next@latest --saveImpact
v12.0.0andv12.0.9We recommend everyone to upgrade regardless of whether you can reproduce the issue or not.
How to Assess Impact
If your server has seen requests to any route under the prefix
/${locale}/_next/that have triggered a heap overflow error, this was caused by the patched issue.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 our users for their investigation and responsible disclosure of the original bug.
We've landed a patch that ensures this is handled properly so the requested route no longer crashes and triggers a heap overflow.
Regression tests for this attack were added to the i18n integration test suite
security@vercel.com. We are actively monitoring this mailbox.Core Changes
process.envto inferred usage: #33186postcss: #33142node-fetch: #33466onLoadingComplete(): #33474next-multilingualexample: #29386lazyRootoptional property tonext/imagecomponent : #33290Documentation Changes
next export+next/imageerror message: #33317onLoadgottcha note tonext/scriptdocs: #33097next/serverdocumentation forgeo: #33609next/imageusage withnext exportbased on feedback.: #33555headersconfig option description: #33484netlify-plugin-cache-nextjshas been deprecated: #33629Example Changes
Misc Changes
Credits
Huge thanks to @molebox, @Schniz, @sokra, @kachkaev, @shuding, @teleaziz, @OgbeniHMMD, @goncy, @balazsorban44, @MaedahBatool, @bennettdams, @kdy1, @huozhi, @hsynlms, @styfle, @ijjk, @callumgare, @jonrosner, @karaggeorge, @rpie3, @MartijnHols, @leerob, @bashunaimiroy, @NOCELL, @rishabhpoddar, @omariosouto, @hanneslund, @theMosaad, @javivelasco, @pierrenel, @lobsterkatie, @tharakabimal, @vvo, @saevarb, @lfades, @nbouvrette, @paulnbrd, @ecklf, @11koukou, @renbaoshuo, @chozzz, @tbezman, @karlhorky, @j-mendez, and @ffan0811 for helping!
v12.0.8Compare Source
Core Changes
<Main />: #32184Writable: #32247nth: #32358jsxtransform of swc: #32383style.filteron image withplaceholder=blur: #32623.nextfolder: #32659placeholder=blur: #32680Configuration
📅 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 has been generated by Mend Renovate. View repository job log here.