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.
References
Link | Resource |
---|---|
https://github.com/vercel/next.js/compare/v13.4.20-canary.12...v13.4.20-canary.13 | Product |
https://github.com/vercel/next.js/issues/45301 | Exploit Issue Tracking Third Party Advisory |
https://github.com/vercel/next.js/pull/54732 | Issue Tracking Patch |
https://github.com/vercel/next.js/compare/v13.4.20-canary.12...v13.4.20-canary.13 | Product |
https://github.com/vercel/next.js/issues/45301 | Exploit Issue Tracking Third Party Advisory |
https://github.com/vercel/next.js/pull/54732 | Issue Tracking Patch |
Configurations
Configuration 1 (hide)
|
History
21 Nov 2024, 08:28
Type | Values Removed | Values Added |
---|---|---|
New CVE |
Information
Published : 2023-10-22 03:15
Updated : 2024-11-21 08:28
NVD link : CVE-2023-46298
Mitre link : CVE-2023-46298
CVE.ORG link : CVE-2023-46298
JSON object : View
Products Affected
vercel
- next.js
CWE