Vitest 0.34.5 is a minor release over version 0.34.4 of this blazing-fast unit testing framework powered by Vite, bringing subtle but important changes for developers. While the core dependencies like cac, chai, and vite remain consistent, reflecting a stable core, the @vitest packages see an update from version 0.34.4 to 0.34.5. Specifically, @vitest/spy, @vitest/utils, @vitest/expect, @vitest/runner, and @vitest/snapshot get bumped, signaling potential bug fixes, performance enhancements, or new features within Vitest's internal testing utilities. Also, vite-node dependency was updated from version 0.34.4 to 0.34.5. These internal package updates are crucial for developers relying on Vitest's mocking, utility, assertion, and snapshotting capabilities.
The devDependencies and peerDependencies sections remain largely unchanged, indicating no significant shifts in the development environment or required peer packages. However, the dist object reveals a slight increase in unpackedSize, suggesting minor additions or modifications to the package's contents. This is also confirmed by the release date, published nearly two weeks after v0.34.4.
For developers, this means a smooth transition with potentially improved core testing functionality. It's advisable to review the changelog or release notes for the @vitest packages and vite-node to understand the precise changes and adapt testing strategies accordingly. Remember to check carefully if you are using this package for unit testing in your projects.
All the vulnerabilities related to the version 0.34.5 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.