CVE-2023-46298
First published: Sun Oct 22 2023(Updated: )
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.
Credit: cve@mitre.org cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| npm/next | >=0.9.9<13.4.20-canary.13 | 13.4.20-canary.13 |
| Next.js | <13.4.20 | |
| Next.js | =13.4.20-canary0 | |
| Next.js | =13.4.20-canary1 | |
| Next.js | =13.4.20-canary10 | |
| Next.js | =13.4.20-canary11 | |
| Next.js | =13.4.20-canary12 | |
| Next.js | =13.4.20-canary2 | |
| Next.js | =13.4.20-canary3 | |
| Next.js | =13.4.20-canary4 | |
| Next.js | =13.4.20-canary5 | |
| Next.js | =13.4.20-canary6 | |
| Next.js | =13.4.20-canary7 | |
| Next.js | =13.4.20-canary8 | |
| Next.js | =13.4.20-canary9 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://github.com/vercel/next.js/compare/v13.4.20-canary.12...v13.4.20-canary.13
- https://github.com/vercel/next.js/issues/45301
- https://github.com/vercel/next.js/pull/54732
- https://nvd.nist.gov/vuln/detail/CVE-2023-46298
- https://github.com/vercel/next.js/commit/20d05958ff853e9c9e42139ffec294336881c648
- https://github.com/advisories/GHSA-c59h-r6p8-q9wc (Advisory)
Frequently Asked Questions
What is CVE-2023-46298?
CVE-2023-46298 is a vulnerability found in Next.js version before 13.4.20-canary.13 that lacks a cache-control header and may cause empty prefetch responses to be cached by a CDN, leading to a denial of service for users.
How does CVE-2023-46298 affect Next.js?
CVE-2023-46298 affects Next.js before version 13.4.20-canary.13 by not including a cache-control header, allowing empty prefetch responses to be cached by a CDN and causing a denial of service for users.
What is the impact of CVE-2023-46298?
The impact of CVE-2023-46298 is a denial of service for users requesting the same URL via a CDN due to the caching of empty prefetch responses.
How can I fix CVE-2023-46298 in Next.js?
To fix CVE-2023-46298 in Next.js, upgrade to version 13.4.20-canary.13 or later, which includes the necessary cache-control header.
Where can I find more information about CVE-2023-46298?
You can find more information about CVE-2023-46298 in the GitHub pull request (https://github.com/vercel/next.js/pull/54732) and issues (https://github.com/vercel/next.js/issues/45301) related to the vulnerability.
- collector/github-advisory-latest
- alias/GHSA-c59h-r6p8-q9wc
- alias/CVE-2023-46298
- collector/github-advisory
- agent/author
- agent/type
- agent/first-publish-date
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/remedy
- agent/references
- agent/description
- agent/last-modified-date
- agent/event
- agent/softwarecombine
- agent/trending
- agent/source
- agent/tags
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- collector/nvd-cve
- package-manager/npm
- vendor/vercel
- canonical/next.js
- version/next.js/13.4.20-canary0
- version/next.js/13.4.20-canary1
- version/next.js/13.4.20-canary10
- version/next.js/13.4.20-canary11
- version/next.js/13.4.20-canary12
- version/next.js/13.4.20-canary2
- version/next.js/13.4.20-canary3
- version/next.js/13.4.20-canary4
- version/next.js/13.4.20-canary5
- version/next.js/13.4.20-canary6
- version/next.js/13.4.20-canary7
- version/next.js/13.4.20-canary8
- version/next.js/13.4.20-canary9