vercel/next.js · Security
Next.js missing cache-control header may lead to CDN caching empty reply
- GHSA ID
- GHSA-c59h-r6p8-q9wc
- CVE ID
- CVE-2023-46298
- Severity
- low
- Published
- Updated
Description
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.
References
- https://nvd.nist.gov/vuln/detail/CVE-2023-46298 ↗
- https://github.com/vercel/next.js/issues/45301 ↗
- https://github.com/vercel/next.js/pull/54732 ↗
- https://github.com/vercel/next.js/compare/v13.4.20-canary.12...v13.4.20-canary.13 ↗
- https://github.com/vercel/next.js/commit/20d05958ff853e9c9e42139ffec294336881c648 ↗
- https://github.com/advisories/GHSA-c59h-r6p8-q9wc ↗