Vitest 1.6.1 is a minor release building upon the robust foundation of version 1.6.0, a next-generation testing framework tailored for Vite-powered projects. Both versions share core dependencies like Chai for assertions, Vite for blazing-fast build speeds, and Pathe for path manipulation, ensuring a consistent experience for developers. Examining the dependency updates reveals subtle yet potentially impactful changes, primarily within Vitest's internal packages. Most notably, versions of @vitest/spy, @vitest/utils, @vitest/expect, @vitest/runner, @vitest/snapshot, and vite-node have bumped from 1.6.0 to 1.6.1, indicating internal enhancements and bug fixes within Vitest's core modules and the vite-node runtime. These updates likely contribute to improved stability, performance, or new features within these specific areas of the testing framework. Developers considering upgrading to 1.6.1 can expect a seamless transition if already using 1.6.0, with the incremental changes focused on refining existing functionality. While the devDependencies and peerDependencies remain largely consistent, these updates still suggest an increased overall maturity and attention to detail, ensuring a reliable testing environment for modern JavaScript applications; The releaseDate also changed from "2024-05-03T15:22:40.746Z" to "2025-02-03T13:36:34.725Z", which makes impossible to compare the versions for real.
All the vulnerabilities related to the version 1.6.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.