@nuxt/vite-builder is a crucial package for Nuxt 3 developers, acting as the Vite bundler that powers the build process. Version 3.12.4 is a patch release over 3.12.3, bringing key updates and potential bug fixes under the hood, ensuring increased stability for your Nuxt applications.
A noteworthy change is the update to the vite dependency, moving from version 5.3.2 to 5.3.4. This likely incorporates performance improvements and bug resolutions within Vite itself that the Nuxt build process can now leverage. There's also an update to @nuxt/kit from version 3.12.3 to 3.12.4, showing tight integration and alignment with the core Nuxt framework.
Furthermore, several dependency version bumps are included. ufo updates from 1.5.3 to 1.5.4, pkg-types moves from 1.1.2 to 1.1.3, and vite-plugin-checker progresses from 0.7.0 to 0.7.2. These updates often encapsulate bug fixes, enhanced features, or security patches within those specific utility libraries. One significant update is within the unenv dependency, moving from 1.9.0 to 1.10.0, likely resulting in better cross-environment compatibility. Finally, rollup is updated in the devDependencies, moving from version 4.18.0 to 4.18.1.
Developers should update to 3.12.4 to benefit from these incremental improvements and ensure they're using the most stable and up-to-date Vite bundler for their Nuxt 3 projects. While the changes may appear minor, incorporating these updates contributes to a smoother, more robust development experience.
All the vulnerabilities related to the version 3.12.4 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.