🚨 [security] Upgrade all of nextjs: 11.1.2 → 12.3.1 (major)

[depfu]

---

Welcome to Depfu 👋

This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.

After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.

Let us know if you have any questions. Thanks so much for giving Depfu a try!

---

---

🚨 Your current dependencies have known security vulnerabilities 🚨

This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!

---

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ eslint-config-next (11.1.2 → 12.3.1)

Sorry, we couldn't find anything useful about this release.

✳️ next (11.1.2 → 12.3.1) · Repo

Security Advisories 🚨

🚨 Unexpected server crash in Next.js

Impact

When specific requests are made to the Next.js server it can cause an unhandledRejection in the server which can crash the process to exit in specific Node.js versions with strict unhandledRejection handling.

• Affected: All of the following must be true to be affected by this CVE

  • Node.js version above v15.0.0 being used with strict unhandledRejection exiting
  • Next.js version v12.2.3
  • Using next start or a custom server

• Not affected: Deployments on Vercel (vercel.com) are not affected along with similar environments where next-server isn't being shared across requests.

Patches

https://github.com/vercel/next.js/releases/tag/v12.2.4

🚨 Improper CSP in Image Optimization API for Next.js versions between 10.0.0 and 12.1.0

Impact

• Affected: All of the following must be true to be affected
  • Next.js between version 10.0.0 and 12.0.10
  • The next.config.js file has images.domains array assigned
  • The image host assigned in images.domains allows user-provided SVG
• Not affected: The next.config.js file has images.loader assigned to something other than default

Patches

Next.js 12.1.0

Workarounds

Change next.config.js to use a different loader configuration other than the default, for example:

module.exports = {
  images: {
    loader: 'imgix',
    path: 'https://example.com/myaccount/',
  },
}

Or if you want to use the loader prop on the component, you can use custom:

module.exports = {
  images: {
    loader: 'custom',
  },
}

🚨 DOS Vulnerability for self-hosted next.js apps using i18n

Impact

Vulnerable code could allow a bad actor to trigger a denial of service attack for anyone running a Next.js app at version >= 12.0.0, and using i18n functionality.

• Affected: All of the following must be true to be affected by this CVE
  • Next.js versions above v12.0.0
  • Using next start or a custom server
  • Using the built-in i18n support
• Not affected:
  • Deployments on Vercel (vercel.com) are not affected along with similar environments where invalid requests are filtered before reaching Next.js.

Patches

A patch has been released, next@12.0.9, that mitigates this issue. We recommend all affected users upgrade as soon as possible.

Workarounds

We recommend upgrading whether you can reproduce or not although you can ensure /${locale}/_next/ is blocked from reaching the Next.js instance until you upgrade.

For more information

If you have any questions or comments about this advisory:

• Open an issue in next
• Email us at security@vercel.com

🚨 Unexpected server crash in Next.js

Next.js is a React framework. In versions of Next.js prior to 12.0.5 or 11.1.3, invalid or malformed URLs could lead to a server crash. In order to be affected by this issue, the deployment must use Next.js versions above 11.1.0 and below 12.0.5, Node.js above 15.0.0, and next start or a custom server. Deployments on Vercel are not affected, along with similar environments where invalid requests are filtered before reaching Next.js. Versions 12.0.5 and 11.1.3 contain patches for this issue.

🚨 Unexpected server crash in Next.js

Next.js is a React framework. In versions of Next.js prior to 12.0.5 or 11.1.3, invalid or malformed URLs could lead to a server crash. In order to be affected by this issue, the deployment must use Next.js versions above 11.1.0 and below 12.0.5, Node.js above 15.0.0, and next start or a custom server. Deployments on Vercel are not affected, along with similar environments where invalid requests are filtered before reaching Next.js. Versions 12.0.5 and 11.1.3 contain patches for this issue.

Release Notes

Too many releases to show here. View the full release notes.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ eslint-plugin-import (indirect, 2.24.2 → 2.26.0) · Repo · Changelog

Release Notes

2.26.0 (from changelog)

Added

• [no-named-default, no-default-export, prefer-default-export, no-named-export, export, named, namespace, no-unused-modules]: support arbitrary module namespace names (#2358, thanks @sosukesuzuki)
• no-dynamic-require: support dynamic import with espree (#2371, thanks @sosukesuzuki)
• no-relative-packages: add fixer (#2381, thanks @forivall)

Fixed

• default: typescript-eslint-parser: avoid a crash on exporting as namespace (thanks @ljharb)
• export/TypeScript: false positive for typescript namespace merging ([#1964], thanks @magarcia)
• no-duplicates: ignore duplicate modules in different TypeScript module declarations (#2378, thanks @remcohaszing)
• no-unused-modules: avoid a crash when processing re-exports (#2388, thanks @ljharb)

Changed

• [Tests] no-nodejs-modules: add tests for node protocol URL (#2367, thanks @sosukesuzuki)
• [Tests] default, no-anonymous-default-export, no-mutable-exports, no-named-as-default-member, no-named-as-default: add tests for arbitrary module namespace names (#2358, thanks @sosukesuzuki)
• [Docs] no-unresolved: Fix RegExp escaping in readme (#2332, thanks @stephtr)
• [Refactor] namespace: try to improve performance (#2340, thanks @ljharb)
• [Docs] make rule doc titles consistent (#2393, thanks @TheJaredWilcurt)
• [Docs] order: TS code examples should use TS code blocks (#2411, thanks [@MM25Zamanian])
• [Docs] no-unresolved: fix link (#2417, thanks @kylemh)

2.25.4 (from changelog)

Fixed

• importType: avoid crashing on a non-string' (#2305, thanks @ljharb)
• first: prevent crash when parsing angular templates (#2210, thanks @ljharb)
• importType: properly resolve @/*-aliased imports as internal (#2334, thanks @ombene)
• named/ExportMap: handle named imports from CJS modules that use dynamic import (#2341, thanks @ludofischer)

Changed

• [no-default-import]: report on the token "default" instead of the entire node (#2299, thanks @pmcelhaney)
• [Docs] order: Remove duplicate mention of default (#2280, thanks @johnthagen)
• [Deps] update eslint-module-utils

2.25.3 (from changelog)

Fixed

• extensions: ignore unresolveable type-only imports (#2270, #2271, @jablko)
• importType: fix isExternalModule calculation (#2282, @mx-bernhard)
• no-import-module-exports: avoid false positives with a shadowed module or exports (#2297, @ljharb)

Changed

• [Docs] order: add type to the default groups (#2272, @charpeni)
• [readme] Add note to TypeScript docs to install appropriate resolver (#2279, @johnthagen)
• [Refactor] importType: combine redundant isScoped and isScopedModule (@ljharb)
• [Docs] HTTP => HTTPS (#2287, @Schweinepriester)

2.25.2

Full Changelog: v2.25.1...v2.25.2

2.25.1

Full Changelog: v2.25.0...v2.25.1

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

🆕 eslint-import-resolver-babel-module (added, 5.3.1)

🆕 sass (added, 1.54.9)

🆕 @​babel/core (added, 7.19.1)

🆕 @​contentful/rich-text-html-renderer (added, 15.13.1)

🆕 @​optimizely/js-sdk-logging (added, 0.3.1)

🆕 @​optimizely/optimizely-sdk (added, 4.9.2)

🆕 @​zeit/next-sass (added, 1.0.1)

🆕 autoprefixer (added, 10.4.12)

🆕 axios (added, 0.25.0)

🆕 babel-loader (added, 8.2.5)

🆕 babel-plugin-module-resolver (added, 4.1.0)

🆕 babel-plugin-wrap-in-js (added, 1.1.1)

🆕 contentful (added, 9.2.4)

🆕 cookie (added, 0.5.0)

🆕 dotenv (added, 16.0.2)

🆕 js-cookie (added, 3.0.1)

🆕 netlify-lambda (added, 2.0.15)

🆕 postcss-easy-import (added, 4.0.0)

🆕 postcss-loader (added, 7.0.1)

🆕 sass-loader (added, 13.0.2)

🆕 uuid (added, 8.3.2)

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

[netlify]

❌ Deploy Preview for optimizely-demo failed.

Name	Link
🔨 Latest commit	ba1a548
🔍 Latest deploy log	https://app.netlify.com/sites/optimizely-demo/deploys/632a6d6e54ffd4000a912ca2