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

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

Open renovate[bot] opened this issue 9 months ago • 2 comments

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
next (source)	`13.5.6` -> `14.1.1`

GitHub Vulnerability Alerts

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-34350

Impact

Inconsistent interpretation of a crafted HTTP request meant that requests are treated as both a single request, and two separate requests by Next.js, leading to desynchronized responses. This led to a response queue poisoning vulnerability in the affected Next.js versions.

For a request to be exploitable, the affected route also had to be making use of the rewrites feature in Next.js.

Patches

The vulnerability is resolved in Next.js 13.5.1 and newer. This includes Next.js 14.x.

Workarounds

There are no official workarounds for this vulnerability. We recommend that you upgrade to a safe version.

References

https://portswigger.net/web-security/request-smuggling/advanced/response-queue-poisoning

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-39693

Impact

A Denial of Service (DoS) condition was identified in Next.js. Exploitation of the bug can trigger a crash, affecting the availability of the server.

This vulnerability can affect all Next.js deployments on the affected versions.

Patches

This vulnerability was resolved in Next.js 13.5 and later. We recommend that users upgrade to a safe version.

Workarounds

There are no official workarounds for this vulnerability.

Credit

We'd like to thank Thai Vu of flyseccorp.com for responsible disclosure of this vulnerability.

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

Release Notes

vercel/next.js (next)

`v14.1.1`

Compare Source

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
Fix trailing slash for canonical url: https://github.com/vercel/next.js/pull/62109
Fix metadata json manifest convention: https://github.com/vercel/next.js/pull/62615
Improve the Server Actions SWC transform: https://github.com/vercel/next.js/pull/61001
Fix Server Reference being double registered: https://github.com/vercel/next.js/pull/61244
Improve the Server Actions SWC transform (part 2): https://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
Fix draft mode invariant: https://github.com/vercel/next.js/pull/62121
fix: babel usage with next/image: https://github.com/vercel/next.js/pull/61835
Fix next/server api alias for ESM pkg: https://github.com/vercel/next.js/pull/61721
Replace image optimizer IPC call with request handler: https://github.com/vercel/next.js/pull/61471
chore: refactor image optimization to separate external/internal urls: https://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
fix(build-output): show stack during CSR bailout warning: https://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
fix(next-swc): Detect exports.foo from cjs_finder: https://github.com/vercel/next.js/pull/61795
Fix attempted import error for react: https://github.com/vercel/next.js/pull/61791
Add stack trace to client rendering bailout error: https://github.com/vercel/next.js/pull/61200
fix router crash on revalidate + popstate: https://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
revert changes to process default routes at build: https://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
Improve redirection handling: https://github.com/vercel/next.js/pull/62561
Simplify node/edge server chunking some: https://github.com/vercel/next.js/pull/62424

Credits

Huge thanks to @huozhi, @shuding, @Ethan-Arrowood, @styfle, @ijjk, @ztanner, @balazsorban44, @kdy1, and @williamli for helping!

Core Changes

Add Next.js 14 codemods to CLI output.: #57552
OpenTelemetry: propagate a configured context(s) to root requests: #57084
debug: Add tags to next build traces to track build configuration in the .next/trace file: #56965
[Traces] Await the flush of the trace write stream to make sure trace file is written: #57641
Add node-pty to externals list: #57640
fix: move logging config validation out of experimental: #57530
Update font data: #57728
Support viewport export via TS Plugin: #57554
Fix: Build compilation warning when using middleware: #57685
chore: Update flight-client-entry-plugin.ts typo: #57734
Improve error for missing default export in dynamic metadata routes: #57711
fix gsp tracing issue: #57766
fix(turbopack): don't match empty route groups: #57647
Update React from 8c8ee9e to 0c63487 and types: #57772

Documentation Changes

Add missing dot in codemod command: #57536
docs(fix): example text unescaped entities: #57255
doc: Clarify built-in support for sass after installation: #57279
Update docs with a Good to know box about using redirect in client components: #56966
docs: fix 02-dynamic-routes.mdx: #57029
Fix incorrect link in GTM docs: #57547
Fix typos: #57592
Add apostrophe 07-error-handling.mdx: #57626
Fix: codemods.mdx Incorrect heading structure of next-og-import, meta…: #57605
Typo fix, version "13" to "14": #57723
Fix Google Tag Manager URL in Third Party Libraries documentation: #57731

Example Changes

Fix: Call cookies function from route to flag as dynamic: #57494
(Examples) Add with-youtube-embed example: #57367
(Examples) Add with-google-maps-embed example: #57365
update @types/react version in examples: #57259
docs: fix broken link to demo: #57229
(example update) Update example with-Clerk: #57050
active-class-name example style js has not taken effect: #56136
add inngest next.js example: #56049
fix inngest example for 3.x sdk: #57712

Misc Changes

update manifest: #57523
update next/third-parties to use Next 14 or 13 as a peer dependency, instead of just 13: #57515
Modify tailwindcss related dependency of create-next-app: #57262
Remove extra CI step and lock Node.js version: #57769

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.

May 10 '24 04:05 renovate[bot]

nextplate nextplate copied to clipboard

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

GitHub Vulnerability Alerts

Impact

Patches

Workarounds

References

Impact

Prerequisites

Patches

Workarounds

Credit

Impact

Patches

Workarounds

Credit

Impact

Patches

Workarounds

Credits

Release Notes

Core Changes

Credits

Core Changes

Documentation Changes

Example Changes

Misc Changes

Credits

Configuration

nextplate
nextplate copied to clipboard