Loading HuntDB...
Hunt
Vulnerability Intelligence by wss.sh
Home Daily Briefings High Impact CVEs Recent Exploits KEV Catalog GitHub Advisories Latest Updates Security News
Sign In Sign Up

CVE-2024-34350

HIGH
Published 2024-05-09T16:07:44.499Z
Actions:

Expert Analysis

Professional remediation guidance

Get tailored security recommendations from our analyst team for CVE-2024-34350. We'll provide specific mitigation strategies based on your environment and risk profile.

CVSS Score

V3.1
7.5
/10
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Base Score Metrics
Exploitability: N/A Impact: N/A

EPSS Score

v2025.03.14
0.005
probability
of exploitation in the wild

There is a 0.5% chance that this vulnerability will be exploited in the wild within the next 30 days.

Updated: 2025-06-25
Exploit Probability
Percentile: 0.648
Higher than 64.8% of all CVEs

Attack Vector Metrics

Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED

Impact Metrics

Confidentiality
NONE
Integrity
HIGH
Availability
NONE

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.

Available Exploits

No exploits available for this CVE.

Related News

No news articles found for this CVE.

Affected Products

vercel

next.js

Affected Versions:

>= 13.4.0, < 13.5.1

GitHub Security Advisories

Community-driven vulnerability intelligence from GitHub

✓ GitHub Reviewed HIGH

Next.js Vulnerable to HTTP Request Smuggling

GHSA-77r5-gw3j-2mpf

Advisory Details

### 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 Packages

npm next
ECOSYSTEM: ≥13.4.0 <13.5.1

CVSS Scoring

CVSS Score

7.5

CVSS Vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:N

References

WEB https://github.com/vercel/next.js/security/advisories/GHSA-77r5-gw3j-2mpf
ADVISORY https://nvd.nist.gov/vuln/detail/CVE-2024-34350
WEB https://github.com/vercel/next.js/commit/44eba020c615f0d9efe431f84ada67b81576f3f5
PACKAGE https://github.com/vercel/next.js
WEB https://github.com/vercel/next.js/compare/v13.5.0...v13.5.1

Advisory provided by GitHub Security Advisory Database. Published: May 9, 2024, Modified: July 9, 2024

References

https://github.com/vercel/next.js/security/advisories/GHSA-77r5-gw3j-2mpf
Published: 2024-05-09T16:07:44.499Z
Last Modified: 2024-08-02T02:51:11.331Z
Copied to clipboard!