Vitest version 0.28.3 represents a minor update to the blazing-fast unit testing framework powered by Vite, building upon the foundation laid by the preceding version 0.28.2. While the core architecture and functionality remain consistent, several subtle yet impactful refinements cater to developers seeking stability and the latest features. The key differences lie primarily within the dependency updates. Most notably, vite-node gets bumped from version 0.28.2 to 0.28.3, and tinypool gains a minor update, moving from 0.3.0 to 0.3.1. Correspondingly, the internal @vitest/* packages are bumped to 0.28.3, ensuring internal consistency. Although subtle, these dependency bumps often incorporate bug fixes and performance improvements essential for optimizing testing workflows.
Developers should appreciate this update as it provides a more polished and refined experience. It demonstrates the vitest team's commitment to maintaining a well-tuned testing environment. The update of vite-node is likely to bring improvements in how vitest interacts with the underlying Vite build system, potentially leading to faster test execution and more accurate module resolution. These enhancements, though subtle, can result in significant time savings over the long run, especially for larger projects with extensive test suites. Upgrading to version 0.28.3 ensures you are leveraging the most current improvements and bug fixes within the vitest ecosystem.
All the vulnerabilities related to the version 0.28.3 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.