Tsup is a zero-config bundler for TypeScript libraries, designed to make the bundling process simple and efficient. Comparing versions 3.10.0 and 3.10.1, it's evident that the updates are subtle but potentially impactful. Both versions share the same core dependencies, including esbuild, rollup, and sucrase, highlighting a consistent approach to bundling and transpilation.
While the dependencies and devDependencies remain virtually identical, the key difference lies in the dist object. Version 3.10.1 has a smaller unpackedSize (576394 bytes) compared to 3.10.0 (579889 bytes), suggesting potential optimizations or minor code trimming. This is something developers should keep in mind, as usually smaller packages result in better build times and performance for their applications.
The only relevant difference found is the releaseDate. Version 3.10.1 was released roughly 2 and a half hours after version 3.10.0, potentially indicating a quick hotfix or minor adjustment based on initial feedback. Developers should consider that tsup still uses a range of popular tools like rollup-plugin-dts, @rollup/plugin-json,postcss and esbuild to effectively bundle TypeScript code, generate declaration files, and optimize code for distribution, making it a powerful choice for modern TypeScript library development.
All the vulnerabilities related to the version 3.10.1 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.