Vitest 0.34.4 is a minor update to the blazing-fast unit testing framework powered by Vite, building upon the solid foundation of version 0.34.3. Both versions maintain the core promise of speed and ease of use, leveraging Vite's rapid bundling capabilities for exceptional testing performance. Key dependencies like cac, chai, pathe, and tinypool remain consistent, ensuring stability and compatibility.
A notable difference lies in the supported Vite versions. Vitest 0.34.4 expands its compatibility, now supporting Vite versions ^3.1.0 || ^4.0.0 || ^5.0.0-0, whereas 0.34.3 supported ^3.0.0 || ^4.0.0. This provides developers with more flexibility in their Vite project configurations. Internal @vitest/* packages were also bumped to align with the 0.34.4 release, fixing bugs and including new features.
For developers, this enhanced Vite compatibility is crucial if they are already using or planning to upgrade to Vite 5. The update ensures smooth integration and avoids potential conflicts. While the core testing experience remains familiar, staying up-to-date with the latest minor version grants access to the most recent bug fixes and performance improvements within the Vitest ecosystem. The unpacked size is slightly bigger in the newer version due to bug fixes and new features. Users are generally advised to update to the newest patch version.
All the vulnerabilities related to the version 0.34.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.