Vitest version 0.29.3 introduces subtle but significant updates compared to its predecessor, version 0.29.2, primarily focusing on internal package dependencies. Developers upgrading from 0.29.2 will notice that the core testing framework remains largely consistent, ensuring minimal disruption to existing test suites.
Key changes lie within the updated dependencies. Most notably, vite-node is updated from version 0.29.2 to 0.29.3 to sync with the primary package version. Also, @vitest/spy, @vitest/utils, @vitest/expect, and @vitest/runner were updated, reflecting internal improvements and bug fixes within Vitest's core modules. While not outwardly visible, these dependency bumps contribute to enhanced stability and performance. The unpacked size increased slightly.
The update provides a seamless transition for developers already leveraging Vitest within their projects, focusing on incremental improvements rather than a radical overhaul. For those new to Vitest, this version offers a robust and performant testing environment, deeply integrated with Vite, benefitting from Vite's speed and configuration simplicity. Both versions target the same peer dependencies. As always, developers should review their test suites and dependency configurations after upgrading, though this minor version bump should generally be low-risk.
All the vulnerabilities related to the version 0.29.3 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.