Vulnerability in Vercel Next.js
CVE-2024-34350
Next.js is a React framework that can provide building blocks to create web applications. Prior to 13.5.1, an 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](https://nextjs.org/docs/app/api-reference/next-config-js/rewrites) feature in Next.js. The vulnerability is resolved in Next.js `13.5.1` and newer.
Vulnerability class: HTTP Request Smuggling
Published · last modified .
CVSS v3 metric
CVSS v3 base score 7.5 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N.
EPSS exploit prediction
EPSS 0.012, 68.4th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Vercel Next.js — versions >= 13.4.0, < 13.5.1
Weakness classification (CWE)
Public exploits and proof-of-concept code
1 public repository with exploit or proof-of-concept code for this CVE:
- Sudistark/rewrites-nextjs-CVE-2024-34350 (last pushed 2024-06-27)
Also mentioned in 4 other repositories (iceberg211/react-custom-ssr, nomi-sec/PoC-in-GitHub, XiaomingX/nice-juejin-article, …). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
This CVE has public exploit evidence. See the latest CVEs with public exploits.