Vitest, a blazing-fast unit test framework powered by Vite, has released version 0.27.3, a minor update following version 0.27.2. Both versions share the same core description and maintain a consistent philosophy of speed and ease of use for developers. Key dependencies like cac, chai, and vite remain largely the same, ensuring compatibility and a familiar development experience. The update appears focused on internal improvements and dependency updates rather than groundbreaking new features. Looking at the dependencies, vite-node advances from version 0.27.2 to 0.27.3 to reflect the release, while the devDependencies show updates for @vitest/ui, @vitest/spy, and @vitest/utils and @vitest/expect, also pointint to version 0.27.3. The size of the package change slightly, fileCount increases from 60 to 61 and unpackedSize from 1446539 to 1451232
Developers already using Vitest can expect a smooth transition, with most code remaining compatible, and can leverage the updates in @vitest/ui, @vitest/spy, @vitest/utils and @vitest/expect for improved testing experiences, more reliable results, and potentially enhanced UI components and utilities. While the changes might seem incremental, such updates solidify Vitest's stability and demonstrate ongoing maintenance, making it a robust choice for projects that desire fast, efficient, and well-supported unit testing. The core benefit of quickly identifying and addressing bugs in your code remains unchanged, as does the seamless integration with Vite's development workflow.
All the vulnerabilities related to the version 0.27.3 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.