Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsUpgrade next
to version 14.2.24, 15.1.6 or higher.
next is a react framework.
Affected versions of this package are vulnerable to Race Condition in the Pages Router
. An attacker can cause the server to serve incorrect pageProps
data instead of the expected HTML content by exploiting a race condition between two requests, one containing the ?__nextDataRequest=1
query parameter and another with the x-now-route-matches
header.
Notes:
This is only exploitable if the CDN provider caches a 200 OK
response even in the absence of explicit cache-control
headers, enabling a poisoned response to persist and be served to subsequent users;
No backend access or privileged escalation is possible through this vulnerability;
Applications hosted on Vercel's platform are not affected by this issue, as the platform does not cache responses based solely on 200 OK
status without explicit cache-control
headers.
This is a bypass of the fix for CVE-2024-46982
This can be mitigated by stripping the x-now-route-matches
header from all incoming requests at your CDN and setting cache-control: no-store
for all responses under risk.