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.
Metrics
Affected Vendors & Products
References
History
Wed, 18 Sep 2024 14:30:00 +0000
Type | Values Removed | Values Added |
---|---|---|
First Time appeared |
Vercel
Vercel next.js |
|
CPEs | cpe:2.3:a:vercel:next.js:*:*:*:*:*:node.js:*:* | |
Vendors & Products |
Vercel
Vercel next.js |
|
Metrics |
ssvc
|
Tue, 17 Sep 2024 22:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
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. | |
Title | Cache Poisoning in next.js | |
Weaknesses | CWE-639 | |
References |
| |
Metrics |
cvssV3_1
|
MITRE
Status: PUBLISHED
Assigner: GitHub_M
Published: 2024-09-17T21:55:04.312Z
Updated: 2024-09-18T13:45:21.409Z
Reserved: 2024-09-16T16:10:09.018Z
Link: CVE-2024-46982
Vulnrichment
Updated: 2024-09-18T13:45:13.928Z
NVD
Status : Awaiting Analysis
Published: 2024-09-17T22:15:02.273
Modified: 2024-09-20T12:30:51.220
Link: CVE-2024-46982
Redhat
No data.