[Snyk] Upgrade next from 9.5.2 to 9.5.5 #841
Open
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 was automatically created by Snyk using the credentials of a real user.
![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)
Snyk has created this PR to upgrade next from 9.5.2 to 9.5.5.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version is 59 versions ahead of your current version.
The recommended version was released on 4 years ago.
Issues fixed by the recommended upgrade:
SNYK-JS-ANSIREGEX-1583908
SNYK-JS-NEXT-1063481
Release notes
Package name: next
Core Changes
Example Changes
Credits
Huge thanks to @ HaNdTriX, and @ jensmeindertsma for helping!
Core Changes
Core Changes
Example Changes
Credits
Huge thanks to @ HaNdTriX and @ jensmeindertsma for helping!
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
npm install next@latest --save
Impact
next export
We recommend everyone to upgrade regardless of whether you can reproduce the issue or not.
How to Assess Impact
If you think users could have been affected, you can filter logs of affected sites by
%2F
with a 308 response.What is Being Done
As Next.js has grown in popularity, it has received the attention of security teams and auditors. We are thankful to those that reached out for their investigation and discovery of the original bug and subsequent responsible disclosure.
We've landed a patch that ensures encoding is handled properly for these types of redirects so the open redirect can no longer occur.
Regression tests for this attack were added to the security integration test suite.
Core Changes
next-head-count
: #16758[email protected]
: Invalid configuration: #17045Documentation Changes
favicon.ico
in static file serving docs.: #17540Example Changes
with-stitches
example: #16827Misc Changes
should
in test name: #17303Credits
Huge thanks to @ YichiZ, @ weichienhung, @ atcastle, @ ijjk, @ seosmmbusiness, @ HsuTing, @ gsimone, @ peduarte, @ Janpot, @ ztanner, @ lfades, @ neighborhood999, @ chibicode, @ merceyz, @ opudalo, @ lunchboxav, @ mohsen1, @ akd-io, @ justman00, @ helloworld, @ devknoll, @ borekb, @ HaNdTriX, @ ArthurMaverick, @ sakito21,