CVE-2024-34350: Next.js Vulnerable to HTTP Request Smuggling

Published May 9, 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 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

Other sources

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 feature in Next.js. The vulnerability is resolved in Next.js 13.5.1 and newer.

MITRE

Affected Software

2 affected componentsFixes available
npm/next>=13.4.0<13.5.1
13.5.1
Vercel Next.js Node.js>=13.4.0<13.5.1

Event History

May 9, 2024
CVE Published
via MITRE·04:07 PM
Data Sourced
via MITRE·04:07 PM
DescriptionSeverityWeakness
Advisory Published
via GitHub·09:07 PM
May 14, 2024
Data Sourced
via NVD·03:38 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·03:38 PM
Affected Software

Frequently Asked Questions

1

What is the severity of CVE-2024-34350?

CVE-2024-34350 has been classified as a moderate severity vulnerability due to its potential for response queue poisoning.

2

How do I fix CVE-2024-34350?

To fix CVE-2024-34350, update Next.js to version 13.5.1 or later.

3

What versions of Next.js are affected by CVE-2024-34350?

CVE-2024-34350 affects Next.js versions between 13.4.0 and 13.5.0.

4

What type of vulnerability is CVE-2024-34350?

CVE-2024-34350 is a response queue poisoning vulnerability caused by inconsistent HTTP request handling.

5

Can CVE-2024-34350 be exploited remotely?

Yes, CVE-2024-34350 can potentially be exploited remotely through crafted HTTP requests.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203