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-server that cannot be parsed, an unhandledPromiseRejection could occur. On Node.js versions v15.0.0, this causes the server process to exit, which can result in unexpected server crashes.
How to Upgrade
We have released patch versions for both the stable and canary channels of Next.js.
To upgrade run npm install next@latest --save
Impact
Affected: All of the following must be true to be affected
Not affected: Deployments on Vercel (vercel.com) are not affected along with similar environments where invalid requests are filtered before reaching Next.js.
We 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.0 with Next.js, you can filter any server error logs for ERR_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-online for their investigation and discovery of the original bug.
We've landed a patch that ensures this is handled properly so the unhandledPromiseRejection issue no longer occurs.
Regression tests for this attack were added to the security integration test suite
A public CVE is requested.
We encourage responsible disclosure of future reports. Please email us at security@vercel.com. We are actively monitoring this mailbox.
Core Changes
Add a swc transform for removal of console.* calls.: #31449
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
- `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language
- `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language
- `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language
- `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language
You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/gregrickaby/nextjs-wordpress-with-apollo/network/alerts).
Bumps next from 12.0.4 to 12.0.5.
Release notes
Sourced from next's releases.
... (truncated)
Commits
b6162bbv12.0.51705020v12.0.5-canary.19f0fd496Revert "Fix running server with Polyfilled fetch (#31935)" (#32100)b194664v12.0.5-canary.18bc429f5Remove future.strictPostcssConfiguration config (#32098)3a5e424Fix the testall npm script (#32081)e58e7b1v12.0.5-canary.176d98b4fEnsure invalid URLs respond with 400 correctly (#32092)1c199a5Fix running server with Polyfilled fetch (#31935)41f87abv12.0.5-canary.16Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/gregrickaby/nextjs-wordpress-with-apollo/network/alerts).