Vitest 0.34.1 represents a minor update to the popular blazing-fast unit test framework, building upon the foundations laid by version 0.34.0. While both versions share the same core dependencies like cac, chai, and vite, ensuring compatibility with existing projects, the key difference lies in the updated versions of internal packages. Specifically, vite-node, @vitest/spy, @vitest/utils, @vitest/expect, @vitest/runner, and @vitest/snapshot have been bumped from 0.34.0 to 0.34.1. These internal dependency updates suggest potential bug fixes, performance improvements, or minor feature enhancements within the Vitest ecosystem.
Developers already using Vitest 0.34.0 will likely find the upgrade to 0.34.1 seamless, with minimal to no breaking changes expected. The focus of this release appears to be on refining the existing functionality rather than introducing major new features. For new users, both versions offer a robust and efficient testing experience, leveraging Vite's speed and familiar configuration. Potential users should consider upgrading to the newest version to benefit from the latest bug fixes and performance improvements, even if the changes appear minor. The relatively short time between the releases of 0.34.0 and 0.34.1 indicates a swift response to any potential issues in the initial release, confirming the team's commitment to providing a stable and well-maintained testing environment.
All the vulnerabilities related to the version 0.34.1 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.