Vitest 0.34.2 represents a minor version bump over its predecessor, version 0.34.1, offering subtle improvements and refinements for developers leveraging this blazing-fast unit testing framework. While both versions share a common foundation, including dependencies like Vite, Chai, and a suite of utilities for spying, expectations, and snapshotting, the update brings underlying enhancements. Core dependencies such as vite-node, @vitest/spy, @vitest/utils, @vitest/expect, @vitest/runner, and @vitest/snapshot have been bumped to version 0.34.2. These internal package updates are designed to improve the overall stability and performance of Vitest. The dist field reveals that version 0.34.2 comes with an increased file count(77 vs 75) and unpacked size (1405347 vs 1368203), suggesting the addition of new features or bug fixes. If you're curious about specific bug fixes, features, changes, it would be recommended to consult the official changelog or release notes for Vitest 0.34.2. The updated release date indicates a refresh of the package and improvements made in a timeframe of approximately 2 weeks. Developers already using Vitest should consider updating to 0.34.2 to benefit from these incremental enhancements and ensure they are running the most stable version. For new users, this version provides a solid entry point into a modern and efficient testing experience.
All the vulnerabilities related to the version 0.34.2 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.