Update dependency next to v9.5.4 [SECURITY] #33
Conversation
This file contains 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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
|
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/thomashighbaugh/startpage/ka7c11sl9 |
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
f1e6761 to
61169fa
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
9.5.2->9.5.4GitHub Vulnerability Alerts
CVE-2020-15242
Impact
next exportWe recommend everyone to upgrade regardless of whether you can reproduce the issue or not.
Patches
https://github.com/zeit/next.js/releases/tag/v9.5.4
References
https://github.com/zeit/next.js/releases/tag/v9.5.4
Release Notes
vercel/next.js
v9.5.4Compare Source
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 --saveImpact
next exportWe 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
%2Fwith 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.icoin static file serving docs.: #17540Example Changes
with-stitchesexample: #16827Misc Changes
shouldin 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, @TrySound, @omBratteng, @svenheden, @hallaji, @kettanaito, @vvo, @m-lautenbach, @jensmeindertsma, @Zeko369, @Timer, @longlho, @stefanprobst, @laugharn, @sdornan, @daneroo, @mohd-akram, @austingmhuang, @sphilee, @devinekadeni, @Bacher, @nghiepit, @tomasdisk, @leader22, @paulogdm, @284km, @belgattitude, @geritol, @stigkj, @sampoder, @samrobbins85, @Pitasi, @digitalPlayer1125, @timfee, @plug-n-play, @philihp, @leerob, @dylanjha, @Kerumen, @rdimaio, @jorisw, @zerbinidamata, @jamesgeorge007, @Jashnm, and @futantan for helping!
v9.5.3Compare Source
Core Changes
configis exported after its declaration: #16211prop-types-exactpackage: #15953<link>attributes in proper order: #16319loadPagetrack success of script loading: #16334/indexrevalidate params: #16451<link rel=stylesheet>on nav: #16537cssText: #16611Documentation Changes
Example Changes
Misc Changes
Credits
Huge thanks to @francisrod01, @kuldeepkeshwar, @tm1000, @ijjk, @khasty720, @Timer, @madiknox, @thorwebdev, @merceyz, @kettanaito, @rafaelalmeidatk, @tuan-m-ng, @cargallo, @chicoxyzzy, @kevva, @iamvishnusankar, @agarwalrounak, @jamesmosier, @louisjuliendo, @timneutkens, @todortotev, @atcastle, @matamatanot, @sclm, @prateekbh, @janicklas-ralph, @crashncrow, @sharils, @lfades, @weichienhung, @khades, @christianpv, @Simply007, @simnalamburt, @jaredpalmer, @longlho, @needcaffeine, @rparet, @Janpot, @samrobbins85, @daneden, @NorbertLuszkiewicz, @piglovesyou, @awareness481, @sakito21, @balazsorban44, @tengmaoqing, @pkrawc, @arthurjdam, and @joris for helping!
Renovate configuration
📅 Schedule: "" (UTC).
🚦 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 WhiteSource Renovate. View repository job log here.