Vitest 0.28.4 represents a minor update to the blazing-fast Vite-powered unit testing framework, building upon the foundation of version 0.28.3. While the core description remains consistent – a tool designed for speed and efficiency in testing JavaScript and TypeScript code – examining the changes reveals subtle yet important enhancements. The primary difference lies within the dependency tree. Notably, the vite-node dependency advances from version 0.28.3 to 0.28.4, suggesting potential bug fixes or performance improvements in how Vitest interacts with Vite's internal modules.
Furthermore, the internal Vitest packages (@vitest/spy, @vitest/utils, @vitest/expect, @vitest/runner) also see version bumps mirroring the main package, moving from 0.28.3 to 0.28.4. This indicates updates to the core testing functionalities, possibly including refined spying capabilities, utility function optimizations, or enhanced assertion handling. While the majority of other dependencies remain the same, developers should be aware that even seemingly small version changes in internal packages can introduce subtle changes in behavior or fix existing issues. The unpacked size also differs slightly, hinting at code adjustments or package structure changes even if dependency versions appear very similar. Users are encouraged to consult the official Vitest changelog for detailed information on specific bug fixes and new features introduced in this release, particularly concerning vite-node and the internal @vitest/* packages, to ensure a smooth upgrade and take full advantage of the refined testing experience.
All the vulnerabilities related to the version 0.28.4 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.