Next.js: Cross-client response injection and disclosure in self-hosted Next.js applications forwarding fetched responses
Affected releases · next
- 16.x16.0.0 – 16.4.4Fixed in 16.4.5
- 15.x15.0.0 – 15.5.28Fixed in 15.5.29
- 14.x14.0.0 – 14.2.35No fix on this line yet
- 13.x and older0.1.0 – 13.5.11No fix, no longer updated
On 16.x, the newest line:
npm install next@16.4.5Every release on a timeline
Affected
16.0.0 – 16.4.4
47 releases
Fixed
16.4.5 – 16.4.6
2 releases
Affected
15.0.0 – 15.5.28
82 releases
Fixed
15.5.29
1 release
Affected
14.0.0 – 14.2.35
46 releases
Affected
13.0.0 – 13.5.11
56 releases
Affected
12.0.0 – 12.3.7
33 releases
Affected
11.0.0 – 11.1.4
7 releases
Affected
10.0.0 – 10.2.3
18 releases
Affected
9.0.0 – 9.5.5
38 releases
Affected
8.0.0 – 8.1.0
6 releases
Affected
7.0.0 – 7.0.3
4 releases
Affected
6.0.0 – 6.1.2
7 releases
Affected
5.0.0 – 5.1.0
2 releases
Affected
4.0.0 – 4.2.3
15 releases
Affected
3.0.1 – 3.2.3
11 releases
Affected
2.0.0 – 2.4.9
17 releases
Affected
1.0.0 – 1.2.3
10 releases
Affected
0.1.0 – 0.9.11
26 releases
What happens
Self-hosted Next.js applications (App Router route handlers and the fetch cache) that return a fetched upstream response unchanged can emit a response whose declared framing does not match the body actually sent. When such an application sits behind an HTTP/1.1 reverse proxy that permits pipelined response queueing, a crafted upstream response can desynchronize responses between clients, enabling response injection and disclosure of other clients' responses.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.