Vitest 2.1.9 represents a minor update to the popular testing framework, building upon the solid foundation of version 2.1.8. While the core functionality remains consistent, several internal dependencies have been bumped, primarily within the Vitest ecosystem itself. Notably, @vitest/spy, @vitest/utils, @vitest/expect, @vitest/mocker, @vitest/runner, and @vitest/pretty-format have all been updated from version 2.1.8 to 2.1.9, ensuring seamless integration and potentially bringing internal improvements and bug fixes. Furthermore, the vite-node dependency has been updated to version 2.1.9.
Developers upgrading to 2.1.9 can anticipate a more cohesive experience within the vitest testing environment. While no groundbreaking features or breaking changes appear evident from the dependency list, these updates likely address minor issues, optimize performance, and enhance overall stability. The consistent versioning across core vitest packages suggests a unified approach to improvements.
The update maintains compatibility with existing peer dependencies, meaning that existing projects using jsdom, happy-dom, @vitest/ui, @types/node, @vitest/browser, and @edge-runtime/vm should experience a smooth transition. Developers can expect the familiar features of Vitest, such as its Vite-powered speed, Jest-compatible API, and TypeScript support, to function as expected. The small increase to unpacked size hints at some internal changes, without being too significant.
All the vulnerabilities related to the version 2.1.9 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.