Vitest 0.29.8 represents a minor update to the blazing-fast Vitest unit testing framework, building upon the solid foundation of version 0.29.7. While the core mission of providing a Vite-powered testing experience remains the same, several refinements and updates have been introduced. The core dependencies received updates, with @vitest/spy, @vitest/utils, @vitest/expect, and @vitest/runner all bumping from 0.29.7 to 0.29.8. These internal package updates likely reflect bug fixes, performance improvements, or feature enhancements within Vitest's core functionalities like mocking, utility functions, expectation library, and test runner, ensuring a more refined and reliable testing process. A key difference is in the dist section, where fileCount and unpackedSize are different. This might reflect changes to the distribution package, perhaps through updated build processes, optimized packaging, or inclusion/exclusion of specific files.
For developers, this upgrade promises a slightly more polished experience. While lacking major version bumps or groundbreaking features, the subtle refinements in core components should translate to a more stable and potentially faster testing workflow. Users are encouraged to update to leverage these improvements and maintain compatibility with the latest Vite ecosystem. A close look at Vitest's changelog will reveal the specific updates made to the impacted testing tools, allowing developers to take full advantage of modifications and repairs in the expectation library, test runner, and more.
All the vulnerabilities related to the version 0.29.8 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.