GHSA-c59h-r6p8-q9wc

Next.js missing cache-control header may lead to CDN caching empty reply

Source: GitHub Advisory Database (reviewed) Low CVE-2023-46298

Packages

Ecosystem	Package	Affected	Fixed in
npm	next	>= 0.9.9, < 13.4.20-canary.13	13.4.20-canary.13

Details

As written in the advisory (Markdown source, shown as plain text).

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

External links from the advisory. They lead to third-party sites.

https://nvd.nist.gov/vuln/detail/CVE-2023-46298 advisory
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 web
https://github.com/vercel/next.js package
https://github.com/vercel/next.js/compare/v13.4.20-canary.12...v13.4.20-canary.13 web