next
Affected
- introduced
13.5.1, fixed13.5.7(semver)
Fixed versions
13.5.7
Fix
- Fixed version
13.5.7npm install [email protected]
Advisory
Also known as: CVE-2024-46982
Next.js Cache Poisoning
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:
pages/dashboard.tsx not pages/blog/[slug].tsxThe below configurations are unaffected:
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
High Basis: The source's own band: HIGH
13.5.1, fixed 13.5.7 (semver)13.5.7
13.5.7npm install [email protected]14.0.0, fixed 14.2.10 (semver)14.2.10
14.2.10npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0