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 v14 [security] #510

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 10, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
next (source) ^13.1.6 -> ^14.0.0 age adoption passing confidence

GitHub Vulnerability Alerts

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

Compare Source

v14.2.6

Compare Source

v14.2.5

Compare Source

v14.2.4

Compare Source

[!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)
  • fix NextRequest proxy in edge runtime (#​66551)
  • Fix next/dynamic with babel and src dir (#​65177)
  • Use vercel deployment url for metadataBase fallbacks (#​65089)
  • fix(next/image): detect react@19 for fetchPriority prop (#​65235)
  • Fix loading navigation with metadata and prefetch (#​66447)
  • prevent duplicate RSC fetch when action redirects (#​66620)
  • ensure router cache updates reference the latest cache values (#​66681)
  • Prevent append of trailing slash in cases where path ends with a file extension (#​66636)
  • Fix inconsistency with 404 getStaticProps cache-control (#​66674)
  • Use addDependency to track metadata route file changes (#​66714)
  • Add timeout/retry handling for fetch cache (#​66652)
  • fix: app-router prefetch crash when an invalid URL is passed to Link (#​66755)
Credits

Huge thanks to @​ztanner, @​ijjk, @​wbinnssmith, @​huozhi, and @​lubieowoce for helping!

v14.2.3

Compare Source

v14.2.2

Compare Source

v14.2.1

Compare Source

v14.2.0

Compare Source

v14.1.4

Compare Source

v14.1.3

Compare Source

v14.1.2

Compare Source

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
Credits

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

v14.1.0

Compare Source

v14.0.4

Compare Source

v14.0.3

Compare Source

v14.0.2

Compare Source

v14.0.1

Compare Source

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

Huge thanks to @​dijonmusters, @​sokra, @​philwolstenholme, @​IgorKowalczyk, @​housseindjirdeh, @​Zoe-Bot, @​HanCiHu, @​JackHowa, @​goncy, @​hirotomoyamada, @​pveyes, @​yeskunall, @​vinaykulk621, @​ChendayUP, @​leerob, @​dvoytenko, @​mknichel, @​ijjk, @​hmaesta, @​ajz003, @​its-kunal, @​joelhooks, @​blurrah, @​tariknh, @​Vinlock, @​Nayeem-XTREME, @​aziyatali, @​aspehler, @​huozhi, @​ztanner, @​ForsakenHarmony, @​moka-ayumu, and @​gnoff for helping!

v14.0.0

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

Copy link

vercel bot commented May 10, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
portfolio ✅ Ready (Inspect) Visit Preview 💬 Add feedback Nov 4, 2024 4:27am

@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from d6bae74 to b5acdd5 Compare May 13, 2024 04:57
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from b5acdd5 to 65a170d Compare May 20, 2024 11:31
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from 65a170d to 03b5d08 Compare May 27, 2024 04:36
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from 03b5d08 to 26922eb Compare June 3, 2024 04:07
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from 26922eb to e0dae17 Compare June 10, 2024 03:35
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from e0dae17 to 6286b50 Compare June 10, 2024 06:12
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from 6286b50 to 2faa6cc Compare June 17, 2024 03:53
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from 2faa6cc to e61ba66 Compare July 6, 2024 00:44
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from e61ba66 to 3f63b68 Compare July 8, 2024 04:13
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from 3f63b68 to b843505 Compare July 15, 2024 03:05
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from b843505 to b0e0e04 Compare July 22, 2024 05:21
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from b0e0e04 to e413a92 Compare August 3, 2024 07:09
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from e413a92 to 2ab247a Compare August 5, 2024 03:17
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from 2ab247a to 2755889 Compare August 12, 2024 04:46
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from 2755889 to 373f879 Compare August 26, 2024 04:05
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from 373f879 to 0f6b57f Compare September 2, 2024 04:41
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from 0f6b57f to a71942a Compare September 9, 2024 04:13
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from a71942a to dc4b9bf Compare September 16, 2024 04:05
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from dc4b9bf to 2ccc4ee Compare September 23, 2024 03:38
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from 2ccc4ee to 35d38b7 Compare September 30, 2024 03:55
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from 35d38b7 to afbc2d4 Compare October 7, 2024 03:39
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from afbc2d4 to c06fbf7 Compare October 14, 2024 03:33
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from c06fbf7 to 1ad6fdb Compare October 21, 2024 03:23
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from 1ad6fdb to 02aaded Compare October 28, 2024 03:44
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.

0 participants