@nuxt/vite-builder versions 3.11.1 and 3.11.0 represent incremental updates to the Vite bundler module within the Nuxt framework, designed to enhance the development experience and optimize production builds. Delving into the dependencies, version 3.11.1 upgrades the postcss dependency from version 8.4.35 to 8.4.36 and @nuxt/kit from 3.11.0 to 3.11.1, introducing potential compatibility improvements or bug fixes related to CSS processing and Nuxt's core functionalities. While both versions share a broad spectrum of dependencies crucial for modern web development – including vite for blazing-fast builds, esbuild for efficient JavaScript transpilation, rollup-plugin-visualizer for bundle analysis, and a suite of tools for Vue 3 compatibility like @vitejs/plugin-vue and @vitejs/plugin-vue-jsx – version 3.11.1 brings subtle refinements aimed at stability and performance.
Developers leveraging @nuxt/vite-builder benefit from seamless integration within the Nuxt ecosystem, offering features such as automatic code splitting, optimized asset handling, and robust support for various CSS preprocessors. The underlying Vite engine ensures hot module replacement (HMR) for rapid development cycles and production-ready bundles optimized for speed. The package's reliance on tools like unplugin and vite-plugin-checker hints at a focus on extensibility through Vite plugins and comprehensive type checking. Furthermore, the inclusion of dependencies like fs-extra, pathe, and ufo suggests utilities for enhanced file system operations, path manipulation, and URL handling, respectively, contributing to a holistic build process tailored for modern Nuxt applications. These changes are likely minor bug fixes and dependency updates, so upgrading is recommended for the most stable experience.
All the vulnerabilities related to the version 3.11.1 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.