GitHub Advisoryadvisory · npm

GHSA-77r5-gw3j-2mpf Next.js Vulnerable to HTTP Request Smuggling

HIGH Published 2024-05-09 Modified 2024-07-09 Official page ↗
Aliases
CVE-2024-34350
Ecosystem
npm
Packages
next
Severity
High
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:N
Weaknesses
CWE-444
Reviewed
2024-05-09

Affected packages

• npm next: >= 13.4.0, < 13.5.1 → fixed in 13.5.1

Description

Impact Inconsistent interpretation of a crafted HTTP request meant that requests are treated as both a single request, and two separate requests by Next.js, leading to desynchronized responses. This led to a response queue poisoning vulnerability in the affected Next.js versions. For a request to be exploitable, the affected route also had to be making use of the rewrites feature in Next.js. Patches The vulnerability is resolved in Next.js `13.5.1` and newer. This includes Next.js `14.x`. Workarounds There are no official workarounds for this vulnerability. We recommend that you upgrade to a safe version. References https://portswigger.net/web-security/request-smuggling/advanced/response-queue-poisoning

Related

Alias · CVE (1)

  • CVE-2024-34350 Next.js is a React framework that can provide building blocks to create web applications. vulnerability

Weakness · CWE (1)

  • CWE-444 Inconsistent Interpretation of HTTP Requests weakness

References