Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Sep 18, 2024

This PR contains the following updates:

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

GitHub Vulnerability Alerts

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

Compare Source

v14.2.9

Compare Source

v14.2.8

Compare Source

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!


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 is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


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

This PR was generated by Mend Renovate. View the repository job log.

@vercel
Copy link

vercel bot commented Sep 18, 2024

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

Name Status Preview Comments Updated (UTC)
react-email ✅ Ready (Inspect) Visit Preview 💬 Add feedback Sep 18, 2024 5:34pm
react-email-demo ✅ Ready (Inspect) Visit Preview 💬 Add feedback Sep 18, 2024 5:34pm

@changeset-bot
Copy link

changeset-bot bot commented Sep 18, 2024

⚠️ No Changeset found

Latest commit: 928f151

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from 4794f42 to 928f151 Compare September 18, 2024 17:28
@gabrielmfern gabrielmfern merged commit 749774d into canary Sep 18, 2024
@gabrielmfern gabrielmfern deleted the renovate/npm-next-vulnerability branch September 18, 2024 17:57
gabrielmfern pushed a commit that referenced this pull request Sep 20, 2024
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
gabrielmfern pushed a commit that referenced this pull request Sep 26, 2024
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
gabrielmfern pushed a commit that referenced this pull request Oct 1, 2024
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
gabrielmfern pushed a commit that referenced this pull request Oct 1, 2024
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
gabrielmfern pushed a commit that referenced this pull request Oct 8, 2024
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
gabrielmfern pushed a commit that referenced this pull request Oct 11, 2024
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
gabrielmfern pushed a commit that referenced this pull request Oct 14, 2024
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
gabrielmfern pushed a commit that referenced this pull request Oct 14, 2024
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
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.

2 participants