Vitest 0.27.1 is a patch release following closely on the heels of version 0.27.0, offering a fast and efficient unit testing framework powered by Vite. While both versions share the same core dependencies like cac, chai, and a compatible Vite range (v3 or v4), the update brings subtle but potentially important refinements. The primary difference lies within the internal tooling and dependency versions. Specifically, vite-node has been updated from 0.27.0 to 0.27.1, and the get-tsconfig devDependency is downgraded from 4.2.0 to 4.3.0. Also, the devDependency ws has been updated from 8.11.0 to 8.12.0, which might bring some improvements on the websocket client. These changes, though seemingly minor, can impact the stability and performance of your tests, especially in complex projects or environments. The patch included an increased file size and unpacked size, from 1433882 to 1443271, that can be related to the version updates. Developers already using Vitest 0.27.0 should consider upgrading to 0.27.1 to benefit from these potential enhancements and bug fixes. New users will naturally start with the latest version, ensuring they have access to the most up-to-date features and improvements. While the listed dependencies seem to be the only files that changed it is important to always update to the latest releases. The release of the latest version was very close after the release of the other so it can be assumed that it contains some fixes.
All the vulnerabilities related to the version 0.27.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.