Vitest 0.25.8 offers subtle but noteworthy enhancements over its predecessor, version 0.25.7, streamlining the testing experience for developers. A primary update lies in the dependencies section, where chai advances from version 4.3.6 to 4.3.7, and acorn moves from 8.8.0 to 8.8.1. Along with @types/chai from 4.3.3 to 4.3.4. These bumps typically incorporate bug fixes and minor feature additions, ensuring better compatibility and stability.
Furthermore, several devDependencies have been tweaked. Happy-dom receives an update from 7.6.6 to 7.8.1, jsdom from 20.0.2 to 20.0.3, magic-string advances from 0.26.7 to 0.27.0, Typescript is updated from 4.8.4 to 4.9.4, @types/prompts updated from 2.4.1 to 2.4.2 and @edge-runtime/vm upgrades from 2.0.1 to 2.0.2, reflecting a continuous effort to leverage the latest tools and improve the development environment. Specifically, the Typescript update from 4.8.4 to 4.9.4 is significant for Typescript users, as it will allow them to use new features and optimizations present in the newer version of Typescript.
The vite-node and @vitest/ui dependencies are also brought in alignment with the parent package version, reflecting general synchronisation. While seemingly incremental, these collective updates address minor issues, enhance performance, and improve overall developer workflow, reinforcing Vitest as a robust and forward-looking testing framework within the Vite ecosystem. The small increase in unpacked size (1542936 to 1543586) shows a minor expansion of the library, but nothing too dramatic.
All the vulnerabilities related to the version 0.25.8 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.