Response queue poisoning via request misinterpretation
Published May 9, 2024 · Updated Aug 2, 2024
HTTP request smuggling in Vercel Next.js 13.4.0 through 13.5.0 allows remote attackers to poison response queues via crafted requests. Request handling for rewritten routes interprets one crafted HTTP message both as a single request and as two requests, desynchronizing queued responses. Exploitation requires an affected route that uses rewrites; the resulting queue mismatch can cause later users to receive misassociated responses.
Summary
What happened
HTTP request smuggling in Vercel Next.js 13.4.0 through 13.5.0 allows remote attackers to poison response queues via crafted requests. Request handling for rewritten routes interprets one crafted HTTP message both as a single request and as two requests, desynchronizing queued responses. Exploitation requires an affected route that uses rewrites; the resulting queue mismatch can cause later users to receive misassociated responses.
The record
- CVE
- CVE-2024-34350
- Published
- May 9, 2024
- Updated
- Aug 2, 2024
- Vendor
- Vercel
- Product
- Next.js
- Classifications
- CWE-444, CAPEC-273, CAPEC-33, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 9, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 13.4.0, < 13.5.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo