Update dependency next to v12.0.5 [SECURITY] #126
Merged
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.4->12.0.5GitHub 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.
Release Notes
vercel/next.js
v12.0.5Compare Source
This upgrade is completely backward-compatible and recommended for all users on versions below 12.0.5. A backport of the patch to Next.js 11 is available as 11.1.3.
When a URL is provided to
next-serverthat cannot be parsed, anunhandledPromiseRejectioncould occur. On Node.js versions <v15.0.0this isn't a fatal issue as only a warning is shown. However, in Node.js versions >v15.0.0, this causes the server process to exit, which can result in unexpected server crashes.How to Upgrade
npm install next@latest --saveImpact
v11.1.0and belowv12.0.5v15.0.0being usednext startor a custom serverWe recommend everyone to upgrade regardless of whether you can reproduce the issue or not.
How to Assess Impact
If you are running Node.js >
v15.0.0with Next.js, you can filter any server error logs forERR_INVALID_URL.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 GitHub user
hopeless-programmer-onlinefor their investigation and discovery of the original bug.We've landed a patch that ensures this is handled properly so the
unhandledPromiseRejectionissue no longer occurs.Regression tests for this attack were added to the security integration test suite
security@vercel.com. We are actively monitoring this mailbox.Core Changes
console.*calls.: #31449next lintwithouteslint-config-nextinstalled: #29823.jsonstatic method: #31483Google-PageRendererbot: #31521Documentcomponents an error: #31505renderToWebStream: #31553no-html-link-for-pagesfrom warning for static files: #31495next/link: #30606pages/_document: #31946Documentation Changes
Suspenseimport: #31897Reactimport: #31900next exportdocumentation.: #31465sharpmemory usage on default Linux setup: #31919Example Changes
with-sentryexample: #30401Misc Changes
Credits
Huge thanks to @mzaien, @losfair, @ykzts, @leerob, @timneutkens, @stefanprobst, @javivelasco, @sokra, @goncy, @knezevicdev, @Kikobeats, @huozhi, @shuding, @styfle, @yang-feng-yfeng, @kdy1, @xuchaobei, @elkevinwolf, @padmaia, @kyliau, @devknoll, @fabienheureux, @hanneslund, @nilskaspersson, @Andarist, @mathcrln, @ijjk, @dferber90, @molebox, @FranciscoMoretti, @benschwarz, @wendellhu95, @gazdagergo, @imabp, @ljosberinn, @samuliasmala, @lfades, @ka2jun8, @monsonjeremy, @pqt, @vvo, @leoortizz, @michel-kraemer, @thibautsabot, @MaedahBatool, @lobsterkatie, @ntkoopman, @delbaoliveira, @iicdii, @j-mendez, @chentsulin, @ericmatthys, @lennym, @balogunkeji, and @wnr for helping!
Configuration
📅 Schedule: "" (UTC).
🚦 Automerge: Disabled due to failing status checks.
♻ 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.