Tsup version 8.3.4 introduces several key updates and dependency upgrades compared to version 8.3.0, potentially impacting developers relying on this zero-config TypeScript bundler. One notable change is the update to esbuild from version 0.23.0 to 0.24.0, which may bring performance improvements and new features in JavaScript and TypeScript compilation. Similarly, rollup is updated from version 4.19.0 to 4.24.0 which will increase the bundling speed and compatibility with latest versions of Node.js. Several direct dependencies also see updates, including cac, debug, and tinyglobby.
On the development dependencies side, sass jumps from version 1.77.8 to 1.80.3, terser upgrades from 5.31.3 to 5.36.0 and @swc/core shifts from 1.7.0 to 1.7.39 which will bring improved stability and fixing of bugs. There's also a notable update to TypeScript going from v5.5.3 toward v5.6.3, ensuring compatibility with more up-to-date typing features. Removing transitive dependencies ensures less security vulnerabilities.
Developers should carefully review these dependency updates, particularly those related to core bundling and compilation tools like esbuild, rollup, and typescript. Testing your project thoroughly after upgrading to tsup v8.3.4 is essential to confirm compatibility and identify any potential breaking changes introduced by these updates, ensuring a smooth transition and leveraging the benefits of the latest improvements, bug fixes and performance enhancements.
All the vulnerabilities related to the version 8.3.4 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.