Tsup is a zero-config tool powered by Rollup and esbuild designed to bundle your TypeScript libraries. This analysis highlights the changes between versions 1.4.9 and 1.4.10. Both versions share the same core dependencies: joycon, rollup, and rollup-plugin-esbuild, fundamental for configuration management and bundling. The development dependencies also remain identical, indicating no alterations to the testing, linting, or type-checking setup. This consistent development environment includes tools like jest for testing, prettier for code formatting, typescript for type checking, and various rollup plugins to handle different module formats.
The key difference resides in the package metadata. Version 1.4.10 of Tsup has a slightly smaller unpacked size (386711 bytes)compared to version 1.4.9 (387428 bytes) despite containing the same number of files. Though a minor difference, it could indicate optimizations in the bundled output or internal library structure. The release date marks a minimal time difference, with 1.4.10 being released shortly after 1.4.9.
For developers using Tsup, this small version jump implies a minor release, likely focusing on bug fixes, performance enhancements, or very subtle internal changes. Given the identical dependency lists, upgrading from 1.4.9 to 1.4.10 should be seamless and risk-free. The core functionality relating to bundling TypeScript libraries with Rollup and esbuild remains consistent between the two versions. Therefore, upgrading is advised to benefit from any potential improvements in size or stability.
All the vulnerabilities related to the version 1.4.10 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.