next 13.5.10 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 14.2.30, 15.2.2 or higher.	>=13.0.0 <14.2.30>=15.0.0-rc.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
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 Server-Side Request Forgery (SSRF) next is a react framework. Affected versions of this package are vulnerable to Server-Side Request Forgery (SSRF) through the `Host` header manipulation. An attacker can make unauthorized requests appearing to originate from the server. Notes: 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 `/`. How to fix Server-Side Request Forgery (SSRF)? Upgrade `next` to version 14.1.1 or higher.	>=13.4.0 <14.1.1

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 14.2.30, 15.2.2 or higher.

>=13.0.0 <14.2.30>=15.0.0-rc.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

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

Server-Side Request Forgery (SSRF)

next is a react framework.

Affected versions of this package are vulnerable to Server-Side Request Forgery (SSRF) through the Host header manipulation. An attacker can make unauthorized requests appearing to originate from the server.

Notes:

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

How to fix Server-Side Request Forgery (SSRF)?

Upgrade next to version 14.1.1 or higher.

>=13.4.0 <14.1.1

next@13.5.10 vulnerabilities

The React Framework

latest version

latest non vulnerable version

first published

latest version published

licenses detected

Direct Vulnerabilities

How to fix?