Vitest 0.26.0 represents a minor version update to the blazing-fast unit test framework powered by Vite, building upon the solid foundation of its predecessor, version 0.25.8. While both versions share core dependencies like Chai, Vite, and a suite of utilities for efficient testing, the key difference lies in the updated vite-node dependency in 0.26.0, aligning it with the core Vitest version. This synchronization ensures a consistent and optimized experience when running tests within the Vite ecosystem.
Developers upgrading to 0.26.0 will benefit from potential performance improvements and bug fixes brought by the vite-node update. The dependency adjustments, though seemingly minor, are critical for maintaining compatibility and stability, particularly for projects heavily relying on Vite's features during testing.
Beyond the core dependencies, the two versions showcase few changes in their devDependencies, as well as peerDependencies, indicating a focus on refining existing functionalities rather than introducing groundbreaking features. Both version offer a comprehensive set of tools for modern testing, including support for mocking, spying, and assertion, ensuring a smooth transition for developers already familiar with Vitest. This commitment to stability and incremental improvement makes Vitest a reliable choice for unit testing in Vite-powered projects.
All the vulnerabilities related to the version 0.26.0 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.