Vitest 0.34.6 introduces subtle but important changes compared to its predecessor, version 0.34.5. Both versions serve as blazing-fast unit testing frameworks powered by Vite, designed to provide developers with a streamlined and efficient testing experience. A primary difference lies in the updated dependencies. Vitest 0.34.6 incorporates a newer version of chai, moving from version 4.3.7 to 4.3.10. Additionally, the internal vite-node dependency is bumped from 0.34.5 to 0.34.6 along with @vitest/spy, @vitest/utils, @vitest/expect, @vitest/runner, @vitest/snapshot internal packages. These updates likely address bug fixes, performance improvements, or incorporate new features within these core dependencies.
Developers should particularly note these changes, as they could impact test behavior or require minor adjustments to existing test suites. The update to chai, a widely used assertion library, might introduce new assertion methods or modify the behavior of existing ones. Keeping an eye on the changelogs of these dependencies is essential for a smooth transition. While the devDependencies and peerDependencies remain consistent, ensuring compatibility with your project's specific tooling and environment is always advisable, especially concerning packages like jsdom, happy-dom, playwright, and webdriverio. Overall, vitest 0.34.6 builds upon the solid foundation of 0.34.5, offering incremental improvements and refinements to enhance the testing workflow.
All the vulnerabilities related to the version 0.34.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.