UNKNOWN npm
Next.js missing cache-control header may lead to CDN caching empty reply
GHSA-c59h-r6p8-q9wc · CVE-2023-46298
Published · Modified
AI SAST
Find this class of vulnerability in your own code
Corgea's AI-native static analysis detects vulnerabilities like this one across your repositories, ranks them by exploitability, and returns review-ready fixes.
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
- ADVISORY https://nvd.nist.gov/vuln/detail/CVE-2023-46298
- WEB https://github.com/vercel/next.js/issues/45301
- WEB https://github.com/vercel/next.js/pull/54732
- WEB https://github.com/vercel/next.js/commit/20d05958ff853e9c9e42139ffec294336881c648
- PACKAGE https://github.com/vercel/next.js
- WEB https://github.com/vercel/next.js/compare/v13.4.20-canary.12...v13.4.20-canary.13
Ready to move
Start Securing
Free, no credit card | First findings in minutes