Tsup is a zero-config TypeScript bundler powered by esbuild, designed for creating modern JavaScript libraries. Version 5.8.0 arrived shortly after 5.7.4, both maintaining the core philosophy of simplicity and ease of use for developers. Comparing the two versions, the most noticeable change isn't in overarching features, but rather refinements and potential bug fixes. Both versions share the same core dependencies like esbuild, rollup, and sucrase, highlighting a consistent approach to bundling and transpilation. The developer dependencies are also almost identical, suggesting a stable development environment. The peer dependency on typescript remains at ^4.2.3, indicating no immediate need to upgrade the TypeScript compiler for either version.
The slight difference in unpackedSize in the dist object (874651 vs 873243 bytes) might hint at minor code adjustments, dependency updates, or even changes in packaging. While seemingly small, these adjustments could translate to improved performance or more efficient builds. Users transitioning from 5.7.4 to 5.8.0 can expect a similar experience overall, with a focus on stability and potentially subtle performance enhancements. Examining the changelog or commit history (if available) would provide more specific details about the changes implemented in version 5.8.0. For developers seeking a straightforward way to bundle TypeScript projects, both versions of Tsup offer a compelling option with minimal configuration.
All the vulnerabilities related to the version 5.8.0 of the package
tsup DOM Clobbering vulnerability
A DOM Clobbering vulnerability in tsup v8.3.4 allows attackers to execute arbitrary code via a crafted script in the import.meta.url to document.currentScript in cjs_shims.js components
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.