Update dependency next to v14 [SECURITY] #535

renovate · 2024-09-25T13:08:31Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
next (source)	`11.1.4` -> `14.2.7`

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

Next.js is a React framework. Starting with version 10.0.0 and prior to version 12.1.0, Next.js is vulnerable to User Interface (UI) Misrepresentation of Critical Information. In order to be affected, the next.config.js file must have an images.domains array assigned and the image host assigned in images.domains must allow user-provided SVG. If the next.config.js file has images.loader assigned to something other than default, the instance is not affected. Version 12.1.0 contains a patch for this issue. As a workaround, change next.config.js to use a different loader configuration other than the default.

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',
  },
}

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)

Update dependency next to v14 [SECURITY] #535

Are you sure you want to change the base?

Update dependency next to v14 [SECURITY] #535

Conversation

renovate bot commented Sep 25, 2024 • edited Loading

GitHub Vulnerability Alerts

Impact

Patches

Workarounds

Impact

Patches

Workarounds

Credits

Release Notes

Core Changes

Credits

Core Changes

Credits

Core Changes

Documentation Changes

Example Changes

Misc Changes

Credits

Core Changes

Credits

Core Changes

Documentation Changes

Example Changes

Misc Changes

Credits

Core Changes

Documentation Changes

Example Changes

Misc Changes

Credits

Core Changes

Configuration

vercel bot commented Sep 25, 2024 • edited Loading

renovate bot commented Sep 25, 2024 •

edited

Loading

vercel bot commented Sep 25, 2024 •

edited

Loading