Vitest 0.32.2 represents a minor version update to the popular blazing-fast unit testing framework powered by Vite. While the core functionality remains consistent, several dependency upgrades and refinements are present, making it a worthwhile update for developers seeking the latest improvements. The most notable change lies in the updated @vitest scoped packages within the dependencies section. Specifically, @vitest/spy, @vitest/utils, @vitest/expect, @vitest/runner, and @vitest/snapshot all see a bump from version 0.32.1 to 0.32.2. This likely signifies bug fixes, performance enhancements, or new features within these core modules of the Vitest framework. Another dependency update is vite-node, going from 0.32.1 to 0.32.2. This means improvements for the vite-node integration used to run your tests, especially useful for projects running Vite in development. While the devDependencies remain largely the same between the two versions, this update ensures developers are leveraging the most current iterations of Vitest's internal tools. Finally, the releaseDate reflects a very recent update, indicating actively maintained and improved codebase for those looking for the most polished testing experience. Upgrading ensures alignment with the latest best practices and potential resolution of any recently identified issues, solidifying Vitest as a reliable and efficient choice for modern JavaScript and TypeScript testing.
All the vulnerabilities related to the version 0.32.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.