Vitest 0.33.0 introduces several updates and refinements compared to version 0.32.4, making it a worthwhile upgrade for developers leveraging this blazing-fast unit testing framework. A key dependency update is vite-node which jumps from 0.32.4 to 0.33.0, indicating potential improvements and bug fixes directly impacting Vite integration. The tinypool dependency also sees an update from 0.5.0 to 0.6.0, possibly delivering enhanced performance and stability in worker thread management.
Furthermore, @vitest scoped packages – @vitest/spy, @vitest/utils, @vitest/expect, @vitest/runner, and @vitest/snapshot – all progress from version 0.32.4 to 0.33.0. This synchronized version bump across core components suggests a cohesive set of enhancements, addressing potential issues and introducing new features across the testing lifecycle, from mocking and utility functions to expectation handling, test execution, and snapshot management. Beyond dependency upgrades, magic-string moves from 0.30.0 to 0.30.1, suggesting minor bug fixes or incremental improvements in source code manipulation and transformation. The file count and unpacked size of the package have slightly increased, suggesting the inclusion of more files or potentially larger code within existing files. Finally, the release date indicates that version 0.33.0 was released just approximately 3 days after the previous one which is common when a bug has a high impact. Developers should consider upgrading to benefit from these targeted updates and refinements, ensuring a smoother and more reliable testing experience.
All the vulnerabilities related to the version 0.33.0 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.