Vitest 0.32.0 arrived shortly after 0.31.4, bringing subtle yet important updates for developers relying on this Vite-powered testing framework. While the core dependencies like cac, chai, and vite remain consistent, the updated version features upgrades to several internal packages, most notably all @vitest/* dependencies jumped from 0.31.4 to 0.32.0. This includes @vitest/spy, @vitest/utils, @vitest/expect, @vitest/runner, and @vitest/snapshot, suggesting improvements and bug fixes within Vitest's core functionalities related to spies, utilities, expectations, test running, and snapshot management.
Another key change is the bump of vite-node from 0.31.4 to 0.32.0, indicating potential enhancements in how Vitest handles Vite's internal functionalities during testing. Also, @edge-runtime/vm was updated from 2.1.2 to 3.0.1 in devDependencies, which might bring benefits when targeting edge runtime environments. Version 0.32.0 was released on June 6th, 2023, marking a quick iteration on the previous stable release from June 1st, 2023, showing the active development and maintenance of Vitest. The unpacked size of the package also increased from 1297370 to 1303744. Users of the library should consider upgrading and checking all the internal packages for detailed changelogs.
All the vulnerabilities related to the version 0.32.0 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.