Vitest version 0.26.1 is a patch release building upon the robust foundation of version 0.26.0, both iterations of this blazing fast unit test framework are powered by Vite, providing developers with a seamless and efficient testing experience. While the core features and dependencies like Chai, Vite, Acorn, and a suite of utilities remain largely consistent, the key distinction lies in incremental updates and bug fixes. Notably, "vite-node" dependency was updated from "0.26.0" to "0.26.1".
Developers leveraging Vitest appreciate its speed, simplicity, and tight integration with the Vite ecosystem. The framework offers a familiar testing syntax, often requiring minimal configuration to get started. Both versions support a wide range of testing scenarios, accommodating both unit and integration tests. The peer dependencies indicate support for various environments, including browser-based testing with jsdom and happy-dom, as well as integration with the Vitest UI for enhanced test reporting and debugging, and edge-runtime compatibility.
The update from 0.26.0 to 0.26.1, although seemingly small, signifies ongoing maintenance and refinement of the testing tool. Developers will find value in upgrading to the latest patch version, 0.26.1, to take advantage of the corrections and improvements provided. It is recommended to check the release notes and changelog for more details on the specific fixes included in the newer version. Differences in file count and unpacked size within the "dist" section suggest variations in bundled assets or documentation updates.
All the vulnerabilities related to the version 0.26.1 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.