Kurz gesagt
- CVE-2024-46982 ist eine Schwachstelle (HOCH (CVSS 7.5)) in next.js (vercel), next.
- Wahrscheinlichkeit einer Ausnutzung in den nächsten 30 Tagen (EPSS): 59.2%, höher als bei 99.1% aller Schwachstellen.
- Abhilfe: auf 13.5.7, 14.2.10 oder neuer aktualisieren.
| Package | Affected versions | Patched versions |
|---|
| next.js | ≥ 13.5.1, < 13.5.7≥ 14.0.0, < 14.2.10
| 13.5.714.2.10
|
| next npm | ≥ 13.5.1, < 13.5.7≥ 14.0.0, < 14.2.10
| 13.5.714.2.10
|
Description
Impact
By sending a crafted HTTP request, it is possible to poison the cache of a non-dynamic server-side rendered route in the pages router (this does not affect the app router). When this crafted request is sent it could coerce Next.js to cache a route that is meant to not be cached and send a Cache-Control: s-maxage=1, stale-while-revalidate header which some upstream CDNs may cache as well.
To be potentially affected all of the following must apply:
- Next.js between 13.5.1 and 14.2.9
- Using pages router
- Using non-dynamic server-side rendered routes e.g.
pages/dashboard.tsx not pages/blog/[slug].tsx
The below configurations are unaffected:
- Deployments using only app router
- Deployments on Vercel are not affected
Patches
This vulnerability was resolved in Next.js v13.5.7, v14.2.10, and later. We recommend upgrading regardless of whether you can reproduce the issue or not.
Workarounds
There are no official or recommended workarounds for this issue, we recommend that users patch to a safe version.
Credits
- Allam Rachid (zhero_)
- Henry Chen
NVD description
Next.js is a React framework for building full-stack web applications. By sending a crafted HTTP request, it is possible to poison the cache of a non-dynamic server-side rendered route in the pages router (this does not affect the app router). When this crafted request is sent it could coerce Next.js to cache a route that is meant to not be cached and send a `Cache-Control: s-maxage=1, stale-while-revalidate` header which some upstream CDNs may cache as well. To be potentially affected all of the following must apply: 1. Next.js between 13.5.1 and 14.2.9, 2. Using pages router, & 3. Using non-dynamic server-side rendered routes e.g. `pages/dashboard.tsx` not `pages/blog/[slug].tsx`. This vulnerability was resolved in Next.js v13.5.7, v14.2.10, and later. We recommend upgrading regardless of whether you can reproduce the issue or not. There are no official or recommended workarounds for this issue, we recommend that users patch to a safe version.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free