next 13.4.4 vulnerabilities

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

Vulnerability	Vulnerable Version
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
H Denial of Service (DoS) next is a react framework. Affected versions of this package are vulnerable to Denial of Service (DoS). An attacker can cause a crash by unspecified means, affecting the availability of the server. How to fix Denial of Service (DoS)? Upgrade `next` to version 13.5.0 or higher.	>=13.4.0 <13.5.0
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
H HTTP Request Smuggling next is a react framework. Affected versions of this package are vulnerable to HTTP Request Smuggling due to the inconsistent interpretation of crafted `HTTP` requests. An attacker can desynchronize server responses and poison the response queue by sending specially crafted HTTP requests that exploit the `rewrites` feature. Note: This patch includes Next.js 14.x. How to fix HTTP Request Smuggling? Upgrade `next` to version 13.5.1 or higher.	>=13.4.0 <13.5.1
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

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

Denial of Service (DoS)

next is a react framework.

Affected versions of this package are vulnerable to Denial of Service (DoS). An attacker can cause a crash by unspecified means, affecting the availability of the server.

How to fix Denial of Service (DoS)?

Upgrade next to version 13.5.0 or higher.

>=13.4.0 <13.5.0

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

HTTP Request Smuggling

next is a react framework.

Affected versions of this package are vulnerable to HTTP Request Smuggling due to the inconsistent interpretation of crafted HTTP requests. An attacker can desynchronize server responses and poison the response queue by sending specially crafted HTTP requests that exploit the rewrites feature.

Note: This patch includes Next.js 14.x.

How to fix HTTP Request Smuggling?

Upgrade next to version 13.5.1 or higher.

>=13.4.0 <13.5.1

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.4.4 vulnerabilities

The React Framework

latest version

latest non vulnerable version

first published

latest version published

licenses detected

Direct Vulnerabilities

How to fix?