Vitest version 0.29.6 represents a minor update over the preceding 0.29.5 release, primarily focusing on internal dependency adjustments. Examining the dependencies section, the core testing framework components like @vitest/spy, @vitest/utils, @vitest/expect, and @vitest/runner, along with vite-node, have been bumped from version 0.29.5 to 0.29.6. This suggests that the update incorporates subtle refinements and potential bug fixes within these modules, which are central to Vitest's functionality.
The devDependencies appear almost identical, indicating that the development environment and associated tooling remain consistent between the two versions. No significant changes were made to tools like jsdom, happy-dom, typescript, or testing-related dependencies. For developers, this means the upgrade is unlikely to introduce breaking changes to their existing test setups or build processes.
The peerDependencies remain unchanged, signifying that external dependencies like @vitest/ui, @vitest/browser, @edge-runtime/vm are still compatible and rely on the same versions.
In conclusion, version 0.29.6 appears to be a maintenance release with improvements to core testing components. For developers already using Vitest, upgrading from 0.29.5 is probably advisable to benefit from possible bug fixes or subtle enhancements in the core modules, without incurring major compatibility issues or requiring significant code modifications. New users shouldn't notice any big differences between the versions, but it's recommended to install the newest stable version from start.
All the vulnerabilities related to the version 0.29.6 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.