Additional changes to review1 matched termMatched wording:no longerThese matches may be harmless in context. Expand to see the excerpts.
- The changelog contains the phrase “no longer”; its impact needs context.
We've landed a patch that ensures encoding is handled properly for these types of redirects so the open redirect can no longer occur.
This upgrade is completely backwards compatible and recommended for all users on versions below 9.5.4. For future security related communications of our OSS projects, please join this mailing list.
A security team from one of our partners noticed an issue in Next.js that allowed for open redirects to occur.
Specially encoded paths could be used with the trailing slash redirect to allow 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 attackers 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
- 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: Users of Next.js between 9.5.0 and 9.5.3
- Not affected: Deployments on Vercel (https://vercel.com) are not affected
- Not affected: Deployments using
next export
We recommend everyone to upgrade regardless of whether you can reproduce the issue or not.