GHSA-77r5-gw3j-2mpf
First published: Thu May 09 2024(Updated: )
### 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](https://nextjs.org/docs/app/api-reference/next-config-js/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
| Affected Software | Affected Version | How to fix |
|---|---|---|
| npm/next | >=13.4.0<13.5.1 | 13.5.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://github.com/vercel/next.js/security/advisories/GHSA-77r5-gw3j-2mpf
- https://github.com/vercel/next.js/commit/44eba020c615f0d9efe431f84ada67b81576f3f5
- https://github.com/vercel/next.js/compare/v13.5.0...v13.5.1
- https://nvd.nist.gov/vuln/detail/CVE-2024-34350
- https://github.com/advisories/GHSA-77r5-gw3j-2mpf (Advisory)
- agent/severity
- agent/weakness
- agent/softwarecombine
- agent/type
- agent/description
- agent/first-publish-date
- agent/event
- collector/github-advisory-latest
- source/GitHub
- alias/GHSA-77r5-gw3j-2mpf
- alias/CVE-2024-34350
- agent/software-canonical-lookup
- agent/last-modified-date
- agent/references
- agent/tags
- collector/github-advisory
- package-manager/npm