Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update dependency next to v9 [security] #82

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 7, 2020

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
next (source) 8.0.1 -> 9.3.2 age adoption passing confidence

GitHub Vulnerability Alerts

CVE-2020-5284

Impact

  • Not affected: Deployments on ZEIT Now v2 (https://zeit.co) are not affected
  • Not affected: Deployments using the serverless target
  • Not affected: Deployments using next export
  • Affected: Users of Next.js below 9.3.2

We 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.2

Compare 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

  • We have released patch versions for both the stable and canary channels of Next.js.
  • To upgrade run npm install next@latest --save

Impact

  • Not affected: Deployments on ZEIT Now v2 (https://zeit.co) are not affected
  • Not affected: Deployments using the serverless target
  • Not affected: Deployments using next export
  • Affected: Users of Next.js below 9.3.2 that use next start

We 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/static are made available under /_next/static.
Regression tests for this attack were added to the security integration test suite.

  • We have notified known Next.js users in advance of this publication.
  • A public CVE was issued.
  • If you want to stay on top of our security related news impacting Next.js or other ZEIT projects, please join this mailing list.
  • We encourage responsible disclosure of future issues. Please email us at security@zeit.co. We are actively monitoring this mailbox.

Patches
  • Add Numeric Separator Support for TypeScript: #​11308
  • Update CLI custom config documentation link: #​11152
  • Add error when attempting to export GSSP page: #​11154
  • Update blog-starter example: #​11071
  • Add CSS file to build output: #​11145
  • Update <dir> reference in help text: 5274535
  • Clean up examples directory: #​11169
  • Remove react-ssr-prepass alias as it's not longer needed: #​11170
  • Upgrade @​ampproject/toolbox-optimizer to 2.0.1: #​11168
  • Add section on reading files: #​11084
  • [Examples] fix remark link in blog-starter's README: #​11177
  • Updated with-typescript example to SSG: #​11081
  • Add CMS example for Sanity: #​10907
  • Group CSS files in shared build output separate from JS files: #​11184
  • Updating min nodejs requirement: #​11181
  • Docs(ssr): req is an IncomingMessage instance, not HttpRequest: #​11194
  • Add support for baseUrl option in tsconfig and jsconfig: #​11203
  • [Example] with-passport: #​10529
  • CMS TakeShape Example: #​11038
  • Ensure hybrid AMP works correctly with SSG: #​11205
  • Update mocha example with yml configuration.: #​11214
  • Fix with-firebase-cloud-messaging example setup code: #​10686
  • Update wording of new data fetching methods recommendation: #​11221
  • Updated Api Routes Middleware example to use getServerSideProps: #​11128
  • With Firebase Client-Side example: #​11053
  • Docs(example): Load basic-css example on codesandbox: #​11227
  • Remove mkdirp, bump fs-extra to 9.0.0: #​11251
  • Add support for paths in tsconfig.json and jsconfig.json: #​11293
  • Add test for single alias: #​11296
  • Update GIP docs: #​11303
  • Add custom amp optimizer and skip validation mode: #​10705
  • Update handling for ENOENT from GSSP methods: #​11302
  • Docs: clarify how to customize next/babel presets: #​11316
  • Fix assignment of props in WithApollo.getInitialProps: #​11236
  • Fix: typo in isStaging in with-env example: #​11305
  • Skip paths that are routed to a .d.ts file: #​11322
  • Upgrade loader-utils: #​11324
  • Fix warning for API routes with next export: #​11330
  • Make sure to copy AMP SSG files during export: #​11331
  • Just a small typo I think, right?: #​11344
  • [docs] Mention our channels: #​11336
  • Use records to init store: #​11343
  • Update data-fetching.md: 074c60e
  • Fix preview-mode docs/examples typo: #​11345
  • Update to prevent re-using workers for getStaticPaths in dev mode: #​11347
Credits

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.1

Compare Source

v9.3.0

Compare Source

v9.2.2

Compare Source

v9.2.1

Compare Source

v9.2.0

Compare Source

v9.1.7

Compare Source

v9.1.6

Compare Source

v9.1.5

Compare Source

v9.1.4

Compare Source

v9.1.3

Compare Source

v9.1.2

Compare Source

v9.1.1

Compare Source

v9.1.0

Compare Source

v9.0.8

Compare Source

v9.0.7

Compare Source

v9.0.6

Compare Source

v9.0.5

Compare Source

v9.0.4

Compare Source

v9.0.3

Compare Source

v9.0.2

Compare Source

v9.0.1

Compare Source

v9.0.0

Compare Source

v8.1.0

Compare Source

v8.0.4

Compare Source

v8.0.3

Compare Source

v8.0.2

Compare Source


Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from 4236146 to 58bbe14 Compare October 20, 2021 05:30
@renovate renovate bot changed the title fix(deps): update dependency next to v9 [security] fix(deps): update dependency next to v11 [security] Oct 20, 2021
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from 58bbe14 to 6e18ffa Compare March 7, 2022 11:31
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from 6e18ffa to 26f4942 Compare April 24, 2022 20:47
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from 26f4942 to 7b50210 Compare May 16, 2022 02:16
@renovate renovate bot changed the title fix(deps): update dependency next to v11 [security] fix(deps): update dependency next to v9 [security] May 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant