Vulnerability 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.
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Vercel | Next.Js | >= 13.4.0, < 13.5.1 |
Related Weaknesses (CWE)
References
- https://github.com/vercel/next.js/security/advisories/GHSA-77r5-gw3j-2mpfVendor Advisory
- https://github.com/vercel/next.js/security/advisories/GHSA-77r5-gw3j-2mpfVendor Advisory
FAQ
What is CVE-2024-34350?
CVE-2024-34350 is a vulnerability with a CVSS score of 7.5 (HIGH). 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 b...
How severe is CVE-2024-34350?
CVE-2024-34350 has been rated HIGH with a CVSS base score of 7.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2024-34350?
Check the references section above for vendor advisories and patch information. Affected products include: Vercel Next.Js.