Vulnerabilities · 2024 · Vercel
CVE-2024-34350
Vercel Next.js vulnerability
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.
Affected products
Next.js. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Vercel Next.js runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/vercel/next.js/security/advisories/GHSA-77r5-gw3j-2mpf · Vendor Advisory
- github.com/vercel/next.js/commit/44eba020c615f0d9efe431f84ada67b81576f3f5
- github.com/vercel/next.js/compare/v13.5.0...v13.5.1
- nvd.nist.gov/vuln/detail/CVE-2024-34350
- github.com/advisories/GHSA-77r5-gw3j-2mpf
- nvd.nist.gov/vuln/detail/CVE-2024-34350
- cve.org/CVERecord?id=CVE-2024-34350
More vulnerabilities in Vercel products
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.