Vitest 0.30.1 is a patch release following closely on the heels of version 0.30.0, both iterations promising a blazing-fast unit testing experience powered by Vite. The core functionality remains consistent, offering developers a seamless transition between the two. Key dependencies such as cac, chai, and vite remain within the same version constraints in both releases, ensuring compatibility and a stable foundation. However, subtle yet important distinctions exist primarily within the versions of internal @vitest packages. Notably, @vitest/spy, @vitest/utils, @vitest/expect, @vitest/runner, and @vitest/snapshot all see version bumps from 0.30.0 to 0.30.1. These updates likely reflect bug fixes, performance improvements or minor feature enhancements within Vitest's internal testing framework, leading to a slightly more optimized testing process. Moreover developers may benefit from an updated vite-node version which steps up from 0.30.0 to 0.30.1. While the detailed changelogs for these minor versions aren't directly included, developers can expect improved stability and potentially refined features related to spying, utility functions, assertions, test running, and snapshot management - critical components for robust unit testing workflows. Developers are encouraged to update to version 0.30.1 to leverage these improvements.
All the vulnerabilities related to the version 0.30.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.