Tsup is a zero-config TypeScript bundler powered by esbuild, designed for creating optimized and efficient JavaScript libraries. Comparing versions 4.8.9 and 4.8.10 reveals subtle yet potentially important updates for developers. Both versions share identical dependencies, devDependencies, and peerDependencies, suggesting no breaking changes or significant feature additions occurred. This consistency implies a focus on stability and refinement rather than radical innovation. Key dependencies like esbuild, rollup, and sucrase enable fast and modern bundling.
The description and core functionality remain unchanged, emphasizing the bundler's intention to stay unopinionated and easy to use. The fileCount in the dist object also stays the same (10), but there's a negligible increase in unpackedSize from 756507 to 756618 between versions. This minor size difference often indicates internal code tweaks, bug fixes, or performance optimizations that don't directly affect the API or configuration. The releaseDate differs by roughly 22 minutes, further supporting the notion of a patch release addressing minor issues promptly.
For developers using Tsup, this implies that upgrading from 4.8.9 to 4.8.10 should be seamless. Users can expect the same familiar workflow and configuration options. The update carries the same peer dependency typescript version. We encourage you to update your packages as soon as possible since issues have been addressed.
All the vulnerabilities related to the version 4.8.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.