Vitest version 0.31.0 introduces several updates and refinements compared to the previous stable version, 0.30.1. Key changes revolve around improvements to its core dependencies and internal packages. Notably, vite-node is updated from version 0.30.1 to 0.31.0, aligning it with the main vitest package version. The vitest-related internal packages like @vitest/spy, @vitest/utils, @vitest/expect, @vitest/runner, and @vitest/snapshot are also bumped from 0.30.1 to 0.31.0, bringing improvements. One dependency, source-map was removed and not present in this new version.
These updates are important for developers as they signify ongoing efforts to enhance Vitest's stability and performance. By syncing internal package versions, the vitest team ensures better cohesion and reduces potential compatibility issues. While the devDependencies remain largely similar, indicating stability in the tooling and testing environment, the core dependencies updates are key for developers leveraging Vitest. These changes can have an impact on performance and stability. The funding URL has also been updated from https://github.com/sponsors/antfu to https://opencollective.com/vitest, which is something interesting for developers who want to support the project. These changes, while seemingly minor version bumps, reflect vital improvements in the vitest testing experience, making it a more reliable and efficient tool for developers.
All the vulnerabilities related to the version 0.31.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.