Nuxt: `__nuxt_island` endpoint does not bind responses to request props, enabling shared-cache poisoning
nuxt
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| nuxt npm |
|
|
| @nuxt/nitro-server npm |
|
nuxt
| Product | Affected | Fixed in |
|---|---|---|
| nuxt npm |
|
|
| @nuxt/nitro-server npm |
|
3.21.64.4.6Nuxt is an open-source web development framework for Vue.js. In Nuxt versions 3.1.0 to before 3.21.6 and 4.0.0-alpha.1 to before 4.4.6 and @nuxt/nitro-server versions 3.20.0 to before 3.21.6 and 4.0.0-alpha.1 to before 4.4.6, the /__nuxt_island/* endpoint accepts attacker-controlled props query/body parameters and renders any island component without verifying that the URL-resident hash (<Name>_<hashId>.json) was actually issued for those inputs by <NuxtIsland>. The hash is computed and embedded client-side but never validated server-side, so the same path can return materially different responses depending on the query. This issue has been patched in versions 3.21.6 and 4.4.6.
From the CVE record · GitHub_M
The /__nuxt_island/* endpoint does not verify that a URL hash was issued for the supplied props. A remote attacker can send attacker-controlled query or body parameters to render an island component and make the same path return different responses. The input does not specify an authentication or user-interaction requirement.
Teams running npm nuxt versions >=3.1.0 <3.21.6 or >=4.0.0-alpha.1 <4.4.6, or @nuxt/nitro-server versions >=3.20.0 <3.21.6 or >=4.2.0 <4.4.6, should check their installations.