Vitest 0.32.3 introduces several incremental improvements over its predecessor, version 0.32.2. Key updates can be observed in the dependencies, reflecting an ongoing effort to stay current with the broader ecosystem. Notably, there are updates to vite-node, @vitest/spy, @vitest/utils, @vitest/expect, @vitest/runner, and @vitest/snapshot, all internal packages within vitest, suggesting improvements or bug fixes within the core testing framework.
In the dependencies section, acorn was updated from version 8.8.2 to 8.9.0 and pathe from 1.1.0 to 1.1.1, while in the devDependencies one can observe multiple updates such as mlly, happy-dom, playwright, @edge-runtime/vm, @sinonjs/fake-timers. The pretty-format dev dependency was updated from 27.5.1 to 29.5.0. All of these updates mean that the vitest team is working to make the testing suite compatible with the most recent versions of these packages.
Specifically, the update to Playwright (from 1.33.0 to 1.35.1) are also beneficial for developers using Vitest for end-to-end testing. These changes likely incorporate the latest features, bug fixes, and performance enhancements offered by these dependencies. Developers relying on these features should consider upgrading. Overall, version 0.32.3 presents a refined and more up-to-date testing environment for Vite projects, with a focus on compatibility and stability.
All the vulnerabilities related to the version 0.32.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.