Nuxt source exposure in development middleware via DNS rebinding
nuxt · @nuxt webpack-builder · @nuxt rspack-builder
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| @nuxt/webpack-builder npm |
|
|
| @nuxt/rspack-builder npm |
|
|
nuxt · @nuxt webpack-builder · @nuxt rspack-builder
| Product | Affected | Fixed in |
|---|---|---|
| @nuxt/webpack-builder npm |
|
|
| @nuxt/rspack-builder npm |
|
|
Nuxt is an open-source web development framework for Vue.js. From @nuxt/webpack-builder 3.0.0 and @nuxt/rspack-builder 3.12.2 until 4.6.4, the development middleware trusts Origin, Referer, or Sec-Fetch-Site when the Host header names the same attacker-controlled hostname. After DNS rebinding changes that hostname to a loopback address, a malicious page opened by a developer can read /_nuxt/*.js client chunks and inline source maps, exposing compiled application source, local filesystem paths, and developer-controlled values embedded in the client bundle. The attacker must know or guess the development-server port and induce the developer to open the malicious page; Chrome 142 and later and other Chromium-based browsers that enforce Local Network Access restrictions prompt before a public page can reach the loopback address. The default Vite builder and production builds are unaffected. This issue is fixed in version 4.6.4.
From the CVE record · GitHub_M
The development middleware in @nuxt/webpack-builder and @nuxt/rspack-builder can trust attacker-controlled request headers after DNS rebinding to a loopback address. A remote attacker who knows or guesses the development-server port and persuades a developer to open a malicious page can read client chunks and inline source maps, exposing compiled application source, local paths, and values embedded in the client bundle. The default Vite builder and production builds are unaffected.
Developers running @nuxt/webpack-builder from 3.0.0 or @nuxt/rspack-builder from 3.12.2 on versions before 4.6.4 should check their installations.