Tsup version 6.2.3 is a minor update to the popular TypeScript bundler, building upon version 6.2.2. While both versions share the core functionality of bundling TypeScript libraries with a zero-config approach powered by esbuild, a closer look reveals subtle yet impactful changes.
The primary difference lies within the dependencies. Version 6.2.3 updates the "bundle-require" dependency from version 3.0.2 to version 3.1.0. This update likely includes bug fixes, performance improvements, or new features related to how Tsup handles dynamic module loading and resolution during the bundling process. Developers who rely on Tsup's ability to bundle code that uses require statements, especially in complex scenarios, might benefit from this update.
Furthermore, looking at the distribution metadata, version 6.2.3 has a slightly larger unpacked size (475424 bytes) compared to version 6.2.2 (475159 bytes), although the file count remains the same at 16. This small size difference might be attributed to the updated bundle-require dependency or potentially very minor internal changes.
For developers already using Tsup, upgrading to version 6.2.3 is generally recommended to take advantage of the dependency update. If you've encountered specific issues with "bundle-require" in previous versions, this update is particularly relevant. If you are new to Tsup, starting with the latest version ensures you are working with the most up-to-date and potentially most stable release. Both versions maintain the same peer dependencies, requiring specific versions of PostCSS, @swc/core, and TypeScript.
All the vulnerabilities related to the version 6.2.3 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.