Vitest 0.28.0 represents an incremental update over version 0.27.3 in this blazing fast unit test framework powered by Vite, offering several refinements that developers should find valuable. The core functionality remains consistent, focusing on speed and ease of use for testing JavaScript and TypeScript codebases. A key addition in 0.28.0 is the introduction of @vitest/spy, @vitest/utils, @vitest/expect, and @vitest/runner as direct dependencies, providing developers with more granular control and access to Vitest's internal utilities for advanced testing scenarios. pathe dependency was also updated from version 0.2.0 to 1.1.0.
The update also involves version bumps for internal dependencies like vite-node and @vitest/ui, ensuring compatibility with the latest Vite ecosystem and incorporating improvements to the user interface for test execution and reporting. While the peer dependencies, like jsdom, happy-dom, @vitest/ui, @vitest/browser, and @edge-runtime/vm, remain the same, developers should ensure their project setup aligns with the requirements of these peer dependencies for optimal performance. This release signifies a continued commitment to refining Vitest, providing a smoother and more powerful testing experience for modern web development projects. The file size is smaller in the new version compared to the previous one.
All the vulnerabilities related to the version 0.28.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.