next 13.3.1-canary.1 vulnerabilities

Known vulnerabilities in the next package. This does not include vulnerabilities belonging to this package’s dependencies.

Vulnerability	Vulnerable Version
L Missing Origin Validation in WebSockets next is a react framework. Affected versions of this package are vulnerable to Missing Origin Validation in WebSockets when running next dev and the project uses the App Router. An attacker can access the source code of client components by exploiting the Cross-site WebSocket hijacking (CSWSH) attack when a user visits a malicious link while having the server running locally. How to fix Missing Origin Validation in WebSockets? Upgrade `next` to version 15.2.2 or higher.	>=13.0.0 <15.2.2
M Race Condition next is a react framework. Affected versions of this package are vulnerable to Race Condition in the `Pages Router`. An attacker can cause the server to serve incorrect `pageProps` data instead of the expected HTML content by exploiting a race condition between two requests, one containing the `?__nextDataRequest=1` query parameter and another with the `x-now-route-matches` header. Notes: This is only exploitable if the CDN provider caches a `200 OK` response even in the absence of explicit `cache-control` headers, enabling a poisoned response to persist and be served to subsequent users; No backend access or privileged escalation is possible through this vulnerability; Applications hosted on Vercel's platform are not affected by this issue, as the platform does not cache responses based solely on `200 OK` status without explicit `cache-control` headers. This is a bypass of the fix for CVE-2024-46982 How to fix Race Condition? Upgrade `next` to version 14.2.24, 15.1.6 or higher.	<14.2.24>=15.0.0 <15.1.6
C Improper Authorization next is a react framework. Affected versions of this package are vulnerable to Improper Authorization due to the improper handling of the `x-middleware-subrequest` header. An attacker can bypass authorization checks by sending crafted requests containing this specific header. How to fix Improper Authorization? Upgrade `next` to version 12.3.5, 13.5.9, 14.2.25, 15.2.3, 15.3.0-canary.12 or higher.	>=11.1.4 <12.3.5>=13.0.0 <13.5.9>=14.0.0 <14.2.25>=15.0.0-rc.0 <15.2.3>=15.3.0-canary.0 <15.3.0-canary.12
M Allocation of Resources Without Limits or Throttling next is a react framework. Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling through the Server Actions process. An attacker can cause the server to hang by constructing requests that leave Server-Actions requests pending until the hosting provider terminates the function execution. Note: This is only exploitable if there are no protections against long-running Server Action invocations. How to fix Allocation of Resources Without Limits or Throttling? Upgrade `next` to version 13.5.8, 14.2.21, 15.1.2 or higher.	>=13.0.0 <13.5.8>=14.0.0 <14.2.21>=15.0.0 <15.1.2
H Missing Authorization next is a react framework. Affected versions of this package are vulnerable to Missing Authorization when using pathname-based checks in middleware for authorization decisions. If i18n configuration is not configured, an attacker can get unintended access to pages one level under the application's root directory. e.g. `https://example.com/foo` is accessible. `https://example.com/` and `https://example.com/foo/bar` are not. Note: Only self-hosted applications are vulnerable. The vulnerability has been fixed by Vercel on the server side. How to fix Missing Authorization? Upgrade `next` to version 13.5.8, 14.2.15, 15.0.0-canary.177 or higher.	>=9.5.5 <13.5.8>=14.0.0 <14.2.15>=15.0.0-canary.0 <15.0.0-canary.177
H Uncontrolled Recursion next is a react framework. Affected versions of this package are vulnerable to Uncontrolled Recursion through the image optimization feature. An attacker can cause excessive CPU consumption by exploiting this vulnerability. How to fix Uncontrolled Recursion? Upgrade `next` to version 14.2.7, 15.0.0-canary.109 or higher.	>=10.0.0 <14.2.7>=15.0.0-canary.0 <15.0.0-canary.109
M Resource Exhaustion next is a react framework. Affected versions of this package are vulnerable to Resource Exhaustion via the `cache-control` header. An attacker can cause a denial of service to all users requesting the same URL via a CDN by caching empty prefetch responses. How to fix Resource Exhaustion? Upgrade `next` to version 13.4.20-canary.13 or higher.	<13.4.20-canary.13

Vulnerability

Vulnerable Version

Missing Origin Validation in WebSockets

next is a react framework.

Affected versions of this package are vulnerable to Missing Origin Validation in WebSockets when running next dev and the project uses the App Router. An attacker can access the source code of client components by exploiting the Cross-site WebSocket hijacking (CSWSH) attack when a user visits a malicious link while having the server running locally.

How to fix Missing Origin Validation in WebSockets?

Upgrade next to version 15.2.2 or higher.

>=13.0.0 <15.2.2

Race Condition

next is a react framework.

Affected versions of this package are vulnerable to Race Condition in the Pages Router. An attacker can cause the server to serve incorrect pageProps data instead of the expected HTML content by exploiting a race condition between two requests, one containing the ?__nextDataRequest=1 query parameter and another with the x-now-route-matches header.

Notes:

This is only exploitable if the CDN provider caches a 200 OK response even in the absence of explicit cache-control headers, enabling a poisoned response to persist and be served to subsequent users;
No backend access or privileged escalation is possible through this vulnerability;
Applications hosted on Vercel's platform are not affected by this issue, as the platform does not cache responses based solely on 200 OK status without explicit cache-control headers.
This is a bypass of the fix for CVE-2024-46982

How to fix Race Condition?

Upgrade next to version 14.2.24, 15.1.6 or higher.

<14.2.24>=15.0.0 <15.1.6

Improper Authorization

next is a react framework.

Affected versions of this package are vulnerable to Improper Authorization due to the improper handling of the x-middleware-subrequest header. An attacker can bypass authorization checks by sending crafted requests containing this specific header.

How to fix Improper Authorization?

Upgrade next to version 12.3.5, 13.5.9, 14.2.25, 15.2.3, 15.3.0-canary.12 or higher.

>=11.1.4 <12.3.5>=13.0.0 <13.5.9>=14.0.0 <14.2.25>=15.0.0-rc.0 <15.2.3>=15.3.0-canary.0 <15.3.0-canary.12

Allocation of Resources Without Limits or Throttling

next is a react framework.

Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling through the Server Actions process. An attacker can cause the server to hang by constructing requests that leave Server-Actions requests pending until the hosting provider terminates the function execution.

Note:

This is only exploitable if there are no protections against long-running Server Action invocations.

How to fix Allocation of Resources Without Limits or Throttling?

Upgrade next to version 13.5.8, 14.2.21, 15.1.2 or higher.

>=13.0.0 <13.5.8>=14.0.0 <14.2.21>=15.0.0 <15.1.2

Missing Authorization

next is a react framework.

Affected versions of this package are vulnerable to Missing Authorization when using pathname-based checks in middleware for authorization decisions. If i18n configuration is not configured, an attacker can get unintended access to pages one level under the application's root directory.

e.g. https://example.com/foo is accessible. https://example.com/ and https://example.com/foo/bar are not.

Note:

Only self-hosted applications are vulnerable. The vulnerability has been fixed by Vercel on the server side.

How to fix Missing Authorization?

Upgrade next to version 13.5.8, 14.2.15, 15.0.0-canary.177 or higher.

>=9.5.5 <13.5.8>=14.0.0 <14.2.15>=15.0.0-canary.0 <15.0.0-canary.177

Uncontrolled Recursion

next is a react framework.

Affected versions of this package are vulnerable to Uncontrolled Recursion through the image optimization feature. An attacker can cause excessive CPU consumption by exploiting this vulnerability.

How to fix Uncontrolled Recursion?

Upgrade next to version 14.2.7, 15.0.0-canary.109 or higher.

>=10.0.0 <14.2.7>=15.0.0-canary.0 <15.0.0-canary.109

Resource Exhaustion

next is a react framework.

Affected versions of this package are vulnerable to Resource Exhaustion via the cache-control header. An attacker can cause a denial of service to all users requesting the same URL via a CDN by caching empty prefetch responses.

How to fix Resource Exhaustion?

Upgrade next to version 13.4.20-canary.13 or higher.

<13.4.20-canary.13

next@13.3.1-canary.1 vulnerabilities

The React Framework

latest version

latest non vulnerable version

first published

latest version published

licenses detected

Direct Vulnerabilities

How to fix?