Vitest version 0.34.3 emerges as a subtle yet important update, building upon the foundation laid by its predecessor, 0.34.2. Both versions maintain the core promise of a blazing-fast unit testing framework for Vite projects, leveraging dependencies like cac, chai, and the Vite ecosystem itself.
The primary distinction lies within the synchronized versions of internal packages such as vite-node, @vitest/spy, @vitest/utils, @vitest/expect, @vitest/runner, and @vitest/snapshot, all moving from 0.34.2 to 0.34.3. This signals a focus on internal consistency and potentially bug fixes or performance improvements within Vitest's core functionalities that might enhance stability and predictability. This synchronization helps developers ensure that all vitest related packages are aligned and working seamlessly.
Furthermore, the slight increase in fileCount and unpackedSize in version 0.34.3 (81 files, 1409978 unpacked size, compared to 77 files and 1405347 for 0.34.2) implies the introduction of new files, or additions, possibly related to documentation, enhanced features, or more comprehensive test coverage.
Developers should prioritise upgrading to 0.34.3 to benefit from the potential internal refinements and improvements regarding its core functionalities, ultimately contributing to a more trustworthy and robust testing experience for their projects. It ensures alignment with the latest advancements within the Vitest ecosystem, ensuring compatibility and support for newer project setups and dependencies.
All the vulnerabilities related to the version 0.34.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.