Tsup version 7.2.0 introduces subtle yet impactful changes compared to the previous stable release, 7.1.0, enhancing the bundling experience for TypeScript libraries. While both versions share core dependencies like esbuild, rollup, and sucrase for efficient code transformation and bundling, the devil's in the details of the development dependencies.
One notable difference is the version of tsup used as a dev dependency within its own project. Version 7.2.0 uses tsup@7.1.0 for internal building, while 7.1.0 uses tsup@6.6.1. It suggest internal testing and potentially bugfixes. Another difference is the update from the rollup-plugin-hashbang that moved from version 2.2.2 to 3.0.0, it could bring some improvements to the hashbang processing. The update to version 7.2.0 also includes general dependency updates, which likely bring performance improvements.
Developers already leveraging Tsup will find the upgrade straightforward, while newcomers can appreciate Tsup's zero-config approach for TypeScript library bundling. Both versions benefit from esbuild's speed, Rollup's plugin ecosystem, and Sucrase's TypeScript support, making Tsup a powerful tool for modern JavaScript development. Keep an eye on the latest releases, as those often contain not only fixes, but also new features to improve the developer experience.
All the vulnerabilities related to the version 7.2.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.