Vitest 0.32.1 is a patch release following closely on the heels of version 0.32.0, both serving as blazing fast unit test frameworks powered by Vite. While both versions share the same core dependencies like cac, chai, and vite, as well as development dependencies such as jsdom, playwright, and webdriverio, the key difference lies in the updated internal dependencies. Specifically, @vitest/expect, @vitest/runner, @vitest/snapshot, @vitest/spy, @vitest/utils and vite-node were bumped up from 0.32.0 to 0.32.1.
For developers, this indicates that version 0.32.1 likely contains bug fixes and minor improvements within Vitest's core modules related to expectations, test running, snapshot management, spying functionalities and utilities. While the broad functionality remains consistent between the two versions, upgrading to 0.32.1 is recommended to benefit from these refinements. New projects should directly adopt the newest version, while existing projects using 0.32.0 should consider updating to leverage these bug fixes and optimizations. The tightly packed release cycle suggests a focus on actively maintaining and improving the stability and reliability of Vitest as a testing solution within the Vite ecosystem, especially for developers depending on Vite-specific features or integrations.
All the vulnerabilities related to the version 0.32.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.