### [CVE-2024-34350](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-34350)
![](https://img.shields.io/static/v1?label=Product&message=next.js&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=%3D%20%3E%3D%2013.4.0%2C%20%3C%2013.5.1%20&color=brighgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-444%3A%20Inconsistent%20Interpretation%20of%20HTTP%20Requests%20('HTTP%20Request%2FResponse%20Smuggling')&color=brighgreen)

### Description

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.

### POC

#### Reference
No PoCs from references.

#### Github
- https://github.com/XiaomingX/weekly
- https://github.com/nomi-sec/PoC-in-GitHub