Vitest version 0.32.4 represents a minor update to the blazing-fast unit test framework, building upon the solid foundation of version 0.32.3. While the core functionality remains consistent, several key dependency updates suggest a focus on improved performance, stability, and compatibility. Specifically, several inner dependencies have been updated such as @vitest/spy, @vitest/utils, @vitest/expect, @vitest/runner, @vitest/snapshot and vite-node, indicating internal refinements to the spying, utility, expectation, runner, snapshot and vite node functionalities which could translate to a smoother testing experience for developers.
Both versions share the same peer dependencies, ensuring continued compatibility with popular testing environments like JSDOM, Happy DOM, Playwright, and WebdriverIO, alongside runtimes like @edge-runtime/vm, giving developers flexibility in their testing setup. The consistent set of devDependencies means existing testing workflows and tooling should remain largely unaffected by this update.
The release date difference between the two versions points to a quick iteration cycle, which is typical of actively maintained projects like Vitest. Developers who prioritize staying current with the latest improvements and bug fixes will find upgrading to version 0.32.4 beneficial. This incremental update underscores Vitest's commitment to providing a reliable, efficient, and continuously evolving testing solution within the Vite ecosystem. Also, the package size has not changed, with both versions having the same file count and unpacked size.
All the vulnerabilities related to the version 0.32.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.