fix(deps): update dependency next to v14 [security]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
next (source)	`^13.4.4` -> `^14.0.0`

GitHub Vulnerability Alerts

Impact

Affected: All of the following must be true to be affected
- Next.js between version 10.0.0 and 11.1.0
- 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
Not affected: Deployments on Vercel are not affected

Patches

Next.js v11.1.1

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. Note that prior version 0.9.9 package next hosted a different utility (0.4.1 being the latest version of that codebase), and this advisory does not apply to those versions.

CVE-2021-37699

Next.js is an open source website development framework to be used with the React library. In affected versions specially encoded paths could be used when pages/_error.js was statically generated, allowing an open redirect to occur to an external site. In general, this redirect does not directly harm users although it can allow for phishing attacks by redirecting to an attacker's domain from a trusted domain.

Impact

Affected: Users of Next.js between 10.0.5 and 10.2.0
Affected: Users of Next.js between 11.0.0 and 11.0.1 using pages/_error.js without getInitialProps
Affected: Users of Next.js between 11.0.0 and 11.0.1 using pages/_error.js and next export
Not affected: Deployments on Vercel (vercel.com) are not affected
Not affected: Deployments with pages/404.js
Note that versions prior to 0.9.9 package next npm package hosted a different utility (0.4.1 being the latest version of that codebase), and this advisory does not apply to those versions.

We recommend upgrading to the latest version of Next.js to improve the overall security of your application.

Patches

https://github.com/vercel/next.js/releases/tag/v11.1.0

CVE-2023-46298

Next.js before 13.4.20-canary.13 lacks a cache-control header and thus empty prefetch responses may sometimes be cached by a CDN, causing a denial of service to all users requesting the same URL via that CDN. Cloudflare considers these requests cacheable assets.

CVE-2024-34351

Impact

A Server-Side Request Forgery (SSRF) vulnerability was identified in Next.js Server Actions by security researchers at Assetnote. If the Host header is modified, and the below conditions are also met, an attacker may be able to make requests that appear to be originating from the Next.js application server itself.

Prerequisites

Next.js (<14.1.1) is running in a self-hosted* manner.
The Next.js application makes use of Server Actions.
The Server Action performs a redirect to a relative path which starts with a /.

* Many hosting providers (including Vercel) route requests based on the Host header, so we do not believe that this vulnerability affects any Next.js applications where routing is done in this manner.

Patches

This vulnerability was patched in #62561 and fixed in Next.js 14.1.1.

Workarounds

There are no official workarounds for this vulnerability. We recommend upgrading to Next.js 14.1.1.

Credit

Vercel and the Next.js team thank Assetnote for responsibly disclosing this issue to us, and for working with us to verify the fix. Thanks to:

Adam Kues - Assetnote Shubham Shah - Assetnote

CVE-2024-46982

Impact

By sending a crafted HTTP request, it is possible to poison the cache of a non-dynamic server-side rendered route in the pages router (this does not affect the app router). When this crafted request is sent it could coerce Next.js to cache a route that is meant to not be cached and send a Cache-Control: s-maxage=1, stale-while-revalidate header which some upstream CDNs may cache as well.

To be potentially affected all of the following must apply:

Next.js between 13.5.1 and 14.2.9
Using pages router
Using non-dynamic server-side rendered routes e.g. pages/dashboard.tsx not pages/blog/[slug].tsx

The below configurations are unaffected:

Deployments using only app router
Deployments on Vercel are not affected

Patches

This vulnerability was resolved in Next.js v13.5.7, v14.2.10, and later. We recommend upgrading regardless of whether you can reproduce the issue or not.

Workarounds

There are no official or recommended workarounds for this issue, we recommend that users patch to a safe version.

Credits

Allam Rachid (zhero_)
Henry Chen

CVE-2024-47831

Impact

The image optimization feature of Next.js contained a vulnerability which allowed for a potential Denial of Service (DoS) condition which could lead to excessive CPU consumption.

Not affected:

The next.config.js file is configured with images.unoptimized set to true or images.loader set to a non-default value.
The Next.js application is hosted on Vercel.

Patches

This issue was fully patched in Next.js 14.2.7. We recommend that users upgrade to at least this version.

Workarounds

Ensure that the next.config.js file has either images.unoptimized, images.loader or images.loaderFile assigned.

Credits

Brandon Dahler (brandondahler), AWS Dimitrios Vlastaras

Release Notes

vercel/next.js (next)

### [`v14.2.7`](https://redirect.github.com/vercel/next.js/compare/v14.2.6...v14.2.7) [Compare Source](https://redirect.github.com/vercel/next.js/compare/v14.2.6...v14.2.7) ### [`v14.2.6`](https://redirect.github.com/vercel/next.js/compare/v14.2.5...v14.2.6) [Compare Source](https://redirect.github.com/vercel/next.js/compare/v14.2.5...v14.2.6) ### [`v14.2.5`](https://redirect.github.com/vercel/next.js/compare/v14.2.4...v14.2.5) [Compare Source](https://redirect.github.com/vercel/next.js/compare/v14.2.4...v14.2.5) ### [`v14.2.4`](https://redirect.github.com/vercel/next.js/releases/tag/v14.2.4) [Compare Source](https://redirect.github.com/vercel/next.js/compare/v14.2.3...v14.2.4) > \[!NOTE]\ > This release is backporting bug fixes. It does **not** include all pending features/changes on canary. ##### Core Changes - fix: ensure route handlers properly track dynamic access ([#66446](https://redirect.github.com/vercel/next.js/issues/66446)) - fix NextRequest proxy in edge runtime ([#66551](https://redirect.github.com/vercel/next.js/issues/66551)) - Fix next/dynamic with babel and src dir ([#65177](https://redirect.github.com/vercel/next.js/issues/65177)) - Use vercel deployment url for metadataBase fallbacks ([#65089](https://redirect.github.com/vercel/next.js/issues/65089)) - fix(next/image): detect react@19 for fetchPriority prop ([#65235](https://redirect.github.com/vercel/next.js/issues/65235)) - Fix loading navigation with metadata and prefetch ([#66447](https://redirect.github.com/vercel/next.js/issues/66447)) - prevent duplicate RSC fetch when action redirects ([#66620](https://redirect.github.com/vercel/next.js/issues/66620)) - ensure router cache updates reference the latest cache values ([#66681](https://redirect.github.com/vercel/next.js/issues/66681)) - Prevent append of trailing slash in cases where path ends with a file extension ([#66636](https://redirect.github.com/vercel/next.js/issues/66636)) - Fix inconsistency with 404 getStaticProps cache-control ([#66674](https://redirect.github.com/vercel/next.js/issues/66674)) - Use addDependency to track metadata route file changes ([#66714](https://redirect.github.com/vercel/next.js/issues/66714)) - Add timeout/retry handling for fetch cache ([#66652](https://redirect.github.com/vercel/next.js/issues/66652)) - fix: app-router prefetch crash when an invalid URL is passed to Link ([#66755](https://redirect.github.com/vercel/next.js/issues/66755)) ##### Credits Huge thanks to [@ztanner](https://redirect.github.com/ztanner), [@ijjk](https://redirect.github.com/ijjk), [@wbinnssmith](https://redirect.github.com/wbinnssmith), [@huozhi](https://redirect.github.com/huozhi), and [@lubieowoce](https://redirect.github.com/lubieowoce) for helping! ### [`v14.2.3`](https://redirect.github.com/vercel/next.js/compare/v14.2.2...v14.2.3) [Compare Source](https://redirect.github.com/vercel/next.js/compare/v14.2.2...v14.2.3) ### [`v14.2.2`](https://redirect.github.com/vercel/next.js/compare/v14.2.1...c850e4a69a8ff62502753e2ff15bbabcea94b556) [Compare Source](https://redirect.github.com/vercel/next.js/compare/v14.2.1...v14.2.2) ### [`v14.2.1`](https://redirect.github.com/vercel/next.js/compare/v14.2.0...v14.2.1) [Compare Source](https://redirect.github.com/vercel/next.js/compare/v14.2.0...v14.2.1) ### [`v14.2.0`](https://redirect.github.com/vercel/next.js/compare/v14.1.4...774563f2b994ae9686b8ec68b506a6ef3d7c9756) [Compare Source](https://redirect.github.com/vercel/next.js/compare/v14.1.4...v14.2.0) ### [`v14.1.4`](https://redirect.github.com/vercel/next.js/compare/v14.1.3...f1fc35730c7aeb0ff39513f91ab2b9ed876393fe) [Compare Source](https://redirect.github.com/vercel/next.js/compare/v14.1.3...v14.1.4) ### [`v14.1.3`](https://redirect.github.com/vercel/next.js/compare/v14.1.2...fc38ee190c9b7de09ebff13a17ebd948cf580ec3) [Compare Source](https://redirect.github.com/vercel/next.js/compare/v14.1.2...v14.1.3) ### [`v14.1.2`](https://redirect.github.com/vercel/next.js/compare/v14.1.1...f564deef86be32a6b25125ddb8172c7c27d3f19a) [Compare Source](https://redirect.github.com/vercel/next.js/compare/v14.1.1...v14.1.2) ### [`v14.1.1`](https://redirect.github.com/vercel/next.js/releases/tag/v14.1.1) [Compare Source](https://redirect.github.com/vercel/next.js/compare/v14.1.0...v14.1.1) *Note: this is a backport release for critical bug fixes -- this does not include all pending features/changes on canary* ##### Core Changes - Should not warn metadataBase missing if only absolute urls are present: [https://github.com/vercel/next.js/pull/61898](https://redirect.github.com/vercel/next.js/pull/61898) - Fix trailing slash for canonical url: [https://github.com/vercel/next.js/pull/62109](https://redirect.github.com/vercel/next.js/pull/62109) - Fix metadata json manifest convention: [https://github.com/vercel/next.js/pull/62615](https://redirect.github.com/vercel/next.js/pull/62615) - Improve the Server Actions SWC transform: [https://github.com/vercel/next.js/pull/61001](https://redirect.github.com/vercel/next.js/pull/61001) - Fix Server Reference being double registered: [https://github.com/vercel/next.js/pull/61244](https://redirect.github.com/vercel/next.js/pull/61244) - Improve the Server Actions SWC transform (part 2): [https://github.com/vercel/next.js/pull/62052](https://redirect.github.com/vercel/next.js/pull/62052) - Fix module-level Server Action creation with closure-closed values: [https://github.com/vercel/next.js/pull/62437](https://redirect.github.com/vercel/next.js/pull/62437) - Fix draft mode invariant: [https://github.com/vercel/next.js/pull/62121](https://redirect.github.com/vercel/next.js/pull/62121) - fix: babel usage with next/image: [https://github.com/vercel/next.js/pull/61835](https://redirect.github.com/vercel/next.js/pull/61835) - Fix next/server api alias for ESM pkg: [https://github.com/vercel/next.js/pull/61721](https://redirect.github.com/vercel/next.js/pull/61721) - Replace image optimizer IPC call with request handler: [https://github.com/vercel/next.js/pull/61471](https://redirect.github.com/vercel/next.js/pull/61471) - chore: refactor image optimization to separate external/internal urls: [https://github.com/vercel/next.js/pull/61172](https://redirect.github.com/vercel/next.js/pull/61172) - fix(image): warn when animated image is missing unoptimized prop: [https://github.com/vercel/next.js/pull/61045](https://redirect.github.com/vercel/next.js/pull/61045) - fix(build-output): show stack during CSR bailout warning: [https://github.com/vercel/next.js/pull/62594](https://redirect.github.com/vercel/next.js/pull/62594) - Fix extra swc optimizer applied to node_modules in browser layer: [https://github.com/vercel/next.js/pull/62051](https://redirect.github.com/vercel/next.js/pull/62051) - fix(next-swc): Detect exports.foo from cjs_finder: [https://github.com/vercel/next.js/pull/61795](https://redirect.github.com/vercel/next.js/pull/61795) - Fix attempted import error for react: [https://github.com/vercel/next.js/pull/61791](https://redirect.github.com/vercel/next.js/pull/61791) - Add stack trace to client rendering bailout error: [https://github.com/vercel/next.js/pull/61200](https://redirect.github.com/vercel/next.js/pull/61200) - fix router crash on revalidate + popstate: [https://github.com/vercel/next.js/pull/62383](https://redirect.github.com/vercel/next.js/pull/62383) - fix loading issue when navigating to page with async metadata: [https://github.com/vercel/next.js/pull/61687](https://redirect.github.com/vercel/next.js/pull/61687) - revert changes to process default routes at build: [https://github.com/vercel/next.js/pull/61241](https://redirect.github.com/vercel/next.js/pull/61241) - fix parallel route top-level catch-all normalization logic to support nested explicit (non-catchall) slot routes: [https://github.com/vercel/next.js/pull/60776](https://redirect.github.com/vercel/next.js/pull/60776) - Improve redirection handling: [https://github.com/vercel/next.js/pull/62561](https://redirect.github.com/vercel/next.js/pull/62561) - Simplify node/edge server chunking some: [https://github.com/vercel/next.js/pull/62424](https://redirect.github.com/vercel/next.js/pull/62424) ##### Credits Huge thanks to [@huozhi](https://redirect.github.com/huozhi), [@shuding](https://redirect.github.com/shuding), [@Ethan-Arrowood](https://redirect.github.com/Ethan-Arrowood), [@styfle](https://redirect.github.com/styfle), [@ijjk](https://redirect.github.com/ijjk), [@ztanner](https://redirect.github.com/ztanner), [@balazsorban44](https://redirect.github.com/balazsorban44), [@kdy1](https://redirect.github.com/kdy1), and [@williamli](https://redirect.github.com/williamli) for helping! ### [`v14.1.0`](https://redirect.github.com/vercel/next.js/compare/v14.0.4...v14.1.0) [Compare Source](https://redirect.github.com/vercel/next.js/compare/v14.0.4...v14.1.0) ### [`v14.0.4`](https://redirect.github.com/vercel/next.js/compare/v14.0.3...v14.0.4) [Compare Source](https://redirect.github.com/vercel/next.js/compare/v14.0.3...v14.0.4) ### [`v14.0.3`](https://redirect.github.com/vercel/next.js/compare/v14.0.2...v14.0.3) [Compare Source](https://redirect.github.com/vercel/next.js/compare/v14.0.2...v14.0.3) ### [`v14.0.2`](https://redirect.github.com/vercel/next.js/compare/v14.0.1...v14.0.2) [Compare Source](https://redirect.github.com/vercel/next.js/compare/v14.0.1...v14.0.2) ### [`v14.0.1`](https://redirect.github.com/vercel/next.js/releases/tag/v14.0.1) [Compare Source](https://redirect.github.com/vercel/next.js/compare/v14.0.0...v14.0.1) ##### Core Changes - Add Next.js 14 codemods to CLI output.: [#57552](https://redirect.github.com/vercel/next.js/issues/57552) - OpenTelemetry: propagate a configured context(s) to root requests: [#57084](https://redirect.github.com/vercel/next.js/issues/57084) - debug: Add tags to next build traces to track build configuration in the .next/trace file: [#56965](https://redirect.github.com/vercel/next.js/issues/56965) - \[Traces] Await the flush of the trace write stream to make sure trace file is written: [#57641](https://redirect.github.com/vercel/next.js/issues/57641) - Add node-pty to externals list: [#57640](https://redirect.github.com/vercel/next.js/issues/57640) - fix: move logging config validation out of experimental: [#57530](https://redirect.github.com/vercel/next.js/issues/57530) - Update font data: [#57728](https://redirect.github.com/vercel/next.js/issues/57728) - Support viewport export via TS Plugin: [#57554](https://redirect.github.com/vercel/next.js/issues/57554) - Fix: Build compilation warning when using middleware: [#57685](https://redirect.github.com/vercel/next.js/issues/57685) - chore: Update flight-client-entry-plugin.ts typo: [#57734](https://redirect.github.com/vercel/next.js/issues/57734) - Improve error for missing default export in dynamic metadata routes: [#57711](https://redirect.github.com/vercel/next.js/issues/57711) - fix gsp tracing issue: [#57766](https://redirect.github.com/vercel/next.js/issues/57766) - fix(turbopack): don't match empty route groups: [#57647](https://redirect.github.com/vercel/next.js/issues/57647) - Update React from [`8c8ee9e`](https://redirect.github.com/vercel/next.js/commit/8c8ee9ee6) to [`0c63487`](https://redirect.github.com/vercel/next.js/commit/0c6348758) and types: [#57772](https://redirect.github.com/vercel/next.js/issues/57772) ##### Documentation Changes - Add missing dot in codemod command: [#57536](https://redirect.github.com/vercel/next.js/issues/57536) - docs(fix): example text unescaped entities: [#57255](https://redirect.github.com/vercel/next.js/issues/57255) - doc: Clarify built-in support for sass after installation: [#57279](https://redirect.github.com/vercel/next.js/issues/57279) - Update docs with a Good to know box about using redirect in client components: [#56966](https://redirect.github.com/vercel/next.js/issues/56966) - docs: fix 02-dynamic-routes.mdx: [#57029](https://redirect.github.com/vercel/next.js/issues/57029) - Fix incorrect link in GTM docs: [#57547](https://redirect.github.com/vercel/next.js/issues/57547) - Fix typos: [#57592](https://redirect.github.com/vercel/next.js/issues/57592) - Add apostrophe 07-error-handling.mdx: [#57626](https://redirect.github.com/vercel/next.js/issues/57626) - Fix: codemods.mdx Incorrect heading structure of next-og-import, meta…: [#57605](https://redirect.github.com/vercel/next.js/issues/57605) - Typo fix, version "13" to "14": [#57723](https://redirect.github.com/vercel/next.js/issues/57723) - Fix Google Tag Manager URL in Third Party Libraries documentation: [#57731](https://redirect.github.com/vercel/next.js/issues/57731) ##### Example Changes - Fix: Call cookies function from route to flag as dynamic: [#57494](https://redirect.github.com/vercel/next.js/issues/57494) - (Examples) Add `with-youtube-embed` example: [#57367](https://redirect.github.com/vercel/next.js/issues/57367) - (Examples) Add `with-google-maps-embed` example: [#57365](https://redirect.github.com/vercel/next.js/issues/57365) - update [@types/react](https://redirect.github.com/types/react) version in examples: [#57259](https://redirect.github.com/vercel/next.js/issues/57259) - docs: fix broken link to demo: [#57229](https://redirect.github.com/vercel/next.js/issues/57229) - (example update) Update example with-Clerk: [#57050](https://redirect.github.com/vercel/next.js/issues/57050) - active-class-name example style js has not taken effect: [#56136](https://redirect.github.com/vercel/next.js/issues/56136) - add inngest next.js example: [#56049](https://redirect.github.com/vercel/next.js/issues/56049) - fix inngest example for 3.x sdk: [#57712](https://redirect.github.com/vercel/next.js/issues/57712) ##### Misc Changes - update manifest: [#57523](https://redirect.github.com/vercel/next.js/issues/57523) - update next/third-parties to use Next 14 or 13 as a peer dependency, instead of just 13: [#57515](https://redirect.github.com/vercel/next.js/issues/57515) - Modify tailwindcss related dependency of `create-next-app`: [#57262](https://redirect.github.com/vercel/next.js/issues/57262) - Remove extra CI step and lock Node.js version: [#57769](https://redirect.github.com/vercel/next.js/issues/57769) ##### Credits Huge thanks to [@dijonmusters](https://redirect.github.com/dijonmusters), [@sokra](https://redirect.github.com/sokra), [@philwolstenholme](https://redirect.github.com/philwolstenholme), [@IgorKowalczyk](https://redirect.github.com/IgorKowalczyk), [@housseindjirdeh](https://redirect.github.com/housseindjirdeh), [@Zoe-Bot](https://redirect.github.com/Zoe-Bot), [@HanCiHu](https://redirect.github.com/HanCiHu), [@JackHowa](https://redirect.github.com/JackHowa), [@goncy](https://redirect.github.com/goncy), [@hirotomoyamada](https://redirect.github.com/hirotomoyamada), [@pveyes](https://redirect.github.com/pveyes), [@yeskunall](https://redirect.github.com/yeskunall), [@vinaykulk621](https://redirect.github.com/vinaykulk621), [@ChendayUP](https://redirect.github.com/ChendayUP), [@leerob](https://redirect.github.com/leerob), [@dvoytenko](https://redirect.github.com/dvoytenko), [@mknichel](https://redirect.github.com/mknichel), [@ijjk](https://redirect.github.com/ijjk), [@hmaesta](https://redirect.github.com/hmaesta), [@ajz003](https://redirect.github.com/ajz003), [@its-kunal](https://redirect.github.com/its-kunal), [@joelhooks](https://redirect.github.com/joelhooks), [@blurrah](https://redirect.github.com/blurrah), [@tariknh](https://redirect.github.com/tariknh), [@Vinlock](https://redirect.github.com/Vinlock), [@Nayeem-XTREME](https://redirect.github.com/Nayeem-XTREME), [@aziyatali](https://redirect.github.com/aziyatali), [@aspehler](https://redirect.github.com/aspehler), [@huozhi](https://redirect.github.com/huozhi), [@ztanner](https://redirect.github.com/ztanner), [@ForsakenHarmony](https://redirect.github.com/ForsakenHarmony), [@moka-ayumu](https://redirect.github.com/moka-ayumu), and [@gnoff](https://redirect.github.com/gnoff) for helping! ### [`v14.0.0`](https://redirect.github.com/vercel/next.js/compare/v13.5.6...v14.0.0) [Compare Source](https://redirect.github.com/vercel/next.js/compare/v13.5.7...v14.0.0) ### [`v13.5.7`](https://redirect.github.com/vercel/next.js/compare/v13.5.6...681d59f76004734c98d5e4e257b75870b50c2402) [Compare Source](https://redirect.github.com/vercel/next.js/compare/v13.5.6...v13.5.7) ### [`v13.5.6`](https://redirect.github.com/vercel/next.js/releases/tag/v13.5.6) [Compare Source](https://redirect.github.com/vercel/next.js/compare/v13.5.5...v13.5.6) ##### Core Changes - Upgrade edge-runtime/cookies [#57021](https://redirect.github.com/vercel/next.js/issues/57021) - Patch React with fix for write-after-close for ReadableStream [#57011](https://redirect.github.com/vercel/next.js/issues/57011) ##### Credits Huge thanks to [@ijjk](https://redirect.github.com/ijjk) [@huozhi](https://redirect.github.com/huozhi) [@gnoff](https://redirect.github.com/gnoff) for helping! ### [`v13.5.5`](https://redirect.github.com/vercel/next.js/compare/v13.5.4...v13.5.5) [Compare Source](https://redirect.github.com/vercel/next.js/compare/v13.5.4...v13.5.5)

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 was generated by Mend Renovate. View the repository job log.

storm-software / stormstack