@nuxt/vite-builder, a crucial Vite bundler for Nuxt applications, has seen a recent update from version 3.13.2 to 3.14.0, bringing several dependency upgrades and potentially impacting build performance and compatibility. Most notably, the core Vite dependency jumps from version 5.4.5 to 5.4.10, incorporating any bug fixes, performance improvements, or new features introduced in that minor release. Similarly, h3 moves from version 1.12.0 to 1.13.0.
Developers should be aware of these dependency bumps and test their Nuxt applications thoroughly after upgrading to ensure compatibility and stability. The update includes also changes in: esbuild(0.23.1 to 0.24.0), unplugin(1.14.1 to 1.15.0), @nuxt/kit(3.13.2 to 3.14.0), vite-node(2.1.1 to 2.1.4), magic-string(0.30.11 to 0.30.12), @vitejs/plugin-vue(5.1.3 to 5.1.4), @rollup/plugin-replace(5.0.7 to 6.0.1), @nuxt/schema(3.13.2 to 3.14.0), vue(3.5.5 to 3.5.12) and rollup(4.21.3 to 4.24.4).
For developers, the upgrade path should be straightforward, but it's advisable to review the changelogs for Vite and other updated dependencies to understand the specifics of each change. These updates likely address bug fixes and could introduce new capabilities or minor breaking changes, so testing is paramount. The updated @nuxt/kit and @nuxt/schema ensures alignment with the latest features and conventions of the Nuxt framework. The newer vue and rollup version brings the lastest improvements for those core dependencies. @nuxt/vite-builder continues its role in streamlining Vite-powered Nuxt builds.
All the vulnerabilities related to the version 3.14.0 of the package
Opening a malicious website while running a Nuxt dev server could allow read-only access to code
Nuxt allows any websites to send any requests to the development server and read the response due to default CORS settings.
While Vite patched the default CORS settings to fix https://github.com/vitejs/vite/security/advisories/GHSA-vg6x-rcgg-rjx6, nuxt uses its own CORS handler by default (https://github.com/nuxt/nuxt/pull/23995).
https://github.com/nuxt/nuxt/blob/7d345c71462d90187fd09c96c7692f306c90def5/packages/vite/src/client.ts#L257-L263
That CORS handler sets Access-Control-Allow-Origin: *.
[!IMPORTANT]
If on an affected version, it may be possible to opt-out of the default Nuxt CORS handler by configuringvite.server.cors.
nuxt dev.http://localhost:3000/_nuxt/app.vue (fetch('http://localhost:3000/_nuxt/app.vue')) from a different origin page.Users with the default server.cors option using Vite builder may get the source code stolen by malicious websites
/__nuxt_vite_node__/manifest / /__nuxt_vite_node__/module also seems to have Access-Control-Allow-Origin: *, so it maybe also possible to exploit that handler.
https://github.com/nuxt/nuxt/blob/7d345c71462d90187fd09c96c7692f306c90def5/packages/vite/src/vite-node.ts#L39
Although I didn't find a valid module id.
Note that this handler is probably also vulnerable to DNS rebinding attacks as I didn't find any host header checks.
esbuild enables any website to send any requests to the development server and read the response
esbuild allows any websites to send any request to the development server and read the response due to default CORS settings.
esbuild sets Access-Control-Allow-Origin: * header to all requests, including the SSE connection, which allows any websites to send any request to the development server and read the response.
https://github.com/evanw/esbuild/blob/df815ac27b84f8b34374c9182a93c94718f8a630/pkg/api/serve_other.go#L121 https://github.com/evanw/esbuild/blob/df815ac27b84f8b34374c9182a93c94718f8a630/pkg/api/serve_other.go#L363
Attack scenario:
http://malicious.example.com).fetch('http://127.0.0.1:8000/main.js') request by JS in that malicious web page. This request is normally blocked by same-origin policy, but that's not the case for the reasons above.http://127.0.0.1:8000/main.js.In this scenario, I assumed that the attacker knows the URL of the bundle output file name. But the attacker can also get that information by
/index.html: normally you have a script tag here/assets: it's common to have a assets directory when you have JS files and CSS files in a different directory and the directory listing feature tells the attacker the list of files/esbuild SSE endpoint: the SSE endpoint sends the URL path of the changed files when the file is changed (new EventSource('/esbuild').addEventListener('change', e => console.log(e.type, e.data)))The scenario above fetches the compiled content, but if the victim has the source map option enabled, the attacker can also get the non-compiled content by fetching the source map file.
npm inpm run watchfetch('http://127.0.0.1:8000/app.js').then(r => r.text()).then(content => console.log(content)) in a different website's dev tools.Users using the serve feature may get the source code stolen by malicious websites.