Next.js missing cache-control header may lead to CDN caching empty reply
Next.js before 13.4.20-canary.13 lacks a cache-control header and thus empty prefetch responses may sometimes be cached by a CDN, causing a denial of service to all users requesting the same URL via that CDN. Cloudflare considers these requests cacheable assets.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2023-46298US | high7.5 | — | ||
Next.js before 13.4.20-canary.13 lacks a cache-control header and thus empty prefetch responses may sometimes be cached by a CDN, causing a denial of service to all users requestin… | ||||
02
references
External citations — patches, advisories, analysis.
- https://github.com/vercel/next.jsPACKAGE
- https://github.com/vercel/next.js/commit/20d05958ff853e9c9e42139ffec294336881c648WEB
- https://github.com/vercel/next.js/compare/v13.4.20-canary.12...v13.4.20-canary.13WEB
- https://github.com/vercel/next.js/issues/45301WEB
- https://github.com/vercel/next.js/pull/54732WEB
- https://nvd.nist.gov/vuln/detail/CVE-2023-46298ADVISORY
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan