CVE-2023-46298
Next.js missing cache-control header may lead to CDN caching empty reply
Overview
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.
Source: OX vulnerability database
Severity
7.5 · HIGH
CVSS 3.1 base score, scored by NVD.
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Affected packages · 1
| Ecosystem | Package | Vulnerable | Fixed in |
|---|---|---|---|
| npm | next | >=0.9.9, <13.4.20-canary.13 | 13.4.20-canary.13 |
Open a package to see all its vulnerabilities.
Operating systems
No Linux distribution reports this ID.
References
- github.com https://github.com/vercel/next.js
- github.com https://github.com/vercel/next.js/commit/20d05958ff853e9c9e42139ffec294336881c648
- github.com https://github.com/vercel/next.js/compare/v13.4.20-canary.12...v13.4.20-canary.13
- github.com https://github.com/vercel/next.js/issues/45301
- github.com https://github.com/vercel/next.js/pull/54732
- nvd.nist.gov https://nvd.nist.gov/vuln/detail/CVE-2023-46298
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.