Tsup is a zero-config TypeScript bundler powered by esbuild, designed for speed and simplicity. Version 5.10.2 introduces a minor update over the previous stable version, 5.10.1, primarily focusing on internal improvements and potentially bug fixes. While the core functionality remains the same, developers may find the updated version more stable and reliable.
Both versions share a robust set of dependencies, including esbuild for blazing-fast bundling, rollup for plugin compatibility and sucrase for faster builds. Key utilities like cac for command-line interface creation and chokidar for file watching are also present. Developers looking for a straightforward way to bundle TypeScript libraries or applications will find Tsup highly valuable because it minimizes the configuration overhead.
The devDependencies lists tools used for development, testing, and building Tsup itself. Notably, both versions support TypeScript 4.2.4 and utilize tools like ava for testing and prettier for code formatting. While the core functionality doesn't drastically change between these versions, upgrading to 5.10.2 may offer a smoother development experience due to resolved issues and potential performance tweaks. Developers should always check the changelog for specific fixes and enhancements. The dist section highlights difference in size showing potentially a minor change in the build output.
All the vulnerabilities related to the version 5.10.2 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.