CyberRota Analysis
AI-GeneratedVersions 12.0.0 through 15.5.20 and 16.0.0 through 16.2.10 of Next.js are vulnerable to a server-side fetch issue that can lead to the leakage of confidential data from POST responses, as cached responses may be returned for requests with different bodies to the same URL. This vulnerability primarily affects applications using fetch calls with mismatched initialization parameters. Developers and organizations utilizing these versions should prioritize upgrading to versions 15.5.21 or 16.2.11 to mitigate potential data exposure risks.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
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.
Related CVEs
Other vulnerabilities affecting the same vendor(s)