Vitest 0.27.2 represents a minor update to the popular Vite-powered unit testing framework, building upon the foundation laid by version 0.27.1. While the core functionality remains consistent, several key dependency updates and internal adjustments have been implemented. The most significant change lies in the updated vite-node dependency, moving from version 0.27.1 to 0.27.2. This likely incorporates bug fixes and performance improvements within the Vite Node integration, enhancing the overall testing experience. Furthermore, @vitest/ui, @vitest/spy, and @vitest/utils, @vitest/expect also receive updates from 0.27.1 to 0.27.2, suggesting refinements and potentially bug fixes within the Vitest UI, spying utilities, internal utilities and expect utilities respectively, contributing to greater stability and reliability. The unpacked size of the package has also increased slightly, which could be due to the mentioned dependency updates that included more code. Developers using Vitest will appreciate these incremental improvements, ensuring a smoother and more robust testing process. This version aims to provide a more stable and efficient testing environment for projects leveraging the Vite ecosystem. Regular updates to dependencies like these contribute to better compatibility with the wider JavaScript ecosystem and ensure developers benefit from the latest advancements in tooling and performance. Therefore, upgrading to 0.27.2 is recommended for users seeking the most up-to-date and refined Vitest experience.
All the vulnerabilities related to the version 0.27.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.