Next.js is a React framework for building full-stack web applications. In versions 12.0.0 through 15.5.20 and 16.0.0 through 16.2.10, a server-side fetch with a request body may return a cached response body from a different request to the same URL but different body. Confidential data in the POST's response body would then leak to unauthorized requests.
Though the request itself will not be deduped. This only applies to fetch calls with a request that has a different init than the one passed to fetch. A safe request would be: fetch(new Request(init), init).
An unsafe request would be: fetch(new Request(init), aDifferentInit). This issue has been fixed in versions 15.5.21 and 16.2.11.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
Low
Easy to exploit
Attack Requirements
Present
Additional conditions required
Privileges Required
None
No privileges needed
User Interaction
Passive
Minimal interaction
Impact Assessment
Confidentiality
High
Complete data leak
Integrity
Low
Partial data modification
Availability
None
No disruption
CVSS Vector v4.0
Weakness Type (CWE)
Vulnerable Products 2
| Configuration | From (including) | Up to (excluding) |
|---|---|---|
|
Vercel Next.Js
cpe:2.3:a:vercel:next.js:*:*:*:*:*:node.js:*:*
|
12.0.0
|
15.5.21
|
|
Vercel Next.Js
cpe:2.3:a:vercel:next.js:*:*:*:*:*:node.js:*:*
|
16.0.0
|
16.2.11
|
References 5
https://github.com/vercel/next.js/commit/062f66700b52a5d6bba2c0605d55577ab7ad26…
security-advisories@github.com
https://github.com/vercel/next.js/commit/73b94872bc343d09494b50394d8c08eb9fc8e5…
security-advisories@github.com
https://github.com/vercel/next.js/releases/tag/v15.5.21
security-advisories@github.com
https://github.com/vercel/next.js/releases/tag/v16.2.11
security-advisories@github.com
https://github.com/vercel/next.js/security/advisories/GHSA-68g3-v927-f742
security-advisories@github.com