@nuxt/vite-builder is a crucial package for Nuxt 3 developers, acting as the bridge between the Nuxt framework and the Vite bundler, enabling faster development builds and optimized production bundles. The latest version, 3.15.4, introduces subtle but important changes compared to the previous stable version, 3.15.3.
While the core dependencies remain largely consistent between the two versions - ensuring compatibility with essential tools like Vite, Vue, and various utility libraries - the key difference lies in the updated @nuxt/kit dependency (3.15.4 in the new version) and rollup devDependency (4.32.1 vs 4.32.0). This suggests improvements and bug fixes within the Nuxt ecosystem itself, potentially leading to enhanced stability and performance for Vite-powered Nuxt applications. Developers should also note the the new version has a slightly bigger packed size and a later release date.
For developers, upgrading to 3.15.4 is recommended to leverage the latest enhancements and bug fixes within the Nuxt 3 ecosystem. Before upgrading, carefully review the Nuxt 3 release notes and any potential breaking changes associated with the updated @nuxt/kit dependency. Though seemingly minor, these incremental updates contribute to a more robust and efficient development experience, allowing developers to focus on building features rather than troubleshooting compatibility issues. Keeping dependencies up-to-date is key to a stable project which unlocks access to the newest features.
All the vulnerabilities related to the version 3.15.4 of the package
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.