The @nuxt/vite-builder package, crucial for integrating the Vite bundler with Nuxt projects, has a new version 3.15.0, offering notable updates compared to the previous stable version 3.14.1592. A significant highlight is the update to Vite itself, jumping from version 5.4.11 to 6.0.5. This brings the performance improvements, new features, and bug fixes inherent in the newer Vite release, potentially leading to faster build times and a smoother development experience.
Other dependency updates of interest include: Jiti (2.4.0 to 2.4.2), unplugin (1.16.0 to 2.1.0), @vitejs/plugin-vue (5.2.0 to 5.2.1), @rollup/plugin-replace (6.0.1 to 6.0.2) and @vitejs/plugin-vue-jsx (4.1.0 to 4.1.1). Esbuild also sees a minor update from 0.24.0 to 0.24.2. These updates often include bug fixes, performance enhancements, and new functionalities that can directly impact the build process and the final application. The update to @nuxt/kit to version 3.15.0 ensures seamless integration with the latest Nuxt features and improvements. Developers should also note the removal of clear as a dependency, along with @types/clear and @types/estree as devDependencies, potentially simplifying the package and build process. This upgrade to version 3.15.0 incorporates a suite of dependency updates, most notably the significant jump in Vite's version, positioning Nuxt developers to leverage the most recent advancements in the Vite ecosystem.
All the vulnerabilities related to the version 3.15.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.