Tsup version 4.6.0 introduces a minor update to the popular zero-config TypeScript bundler, building upon the solid foundation established in version 4.5.1. While the core functionality remains consistent, the upgrade brings subtle refinements and dependency adjustments that developers should be aware of. Both versions share the same core dependencies and devDependencies, including esbuild, rollup, sucrase, typescript and the familiar tooling around testing, linting and formatting through jest, prettier and other plugins.
A key differentiator lies in the distribution size where version 4.6.0 sees a small increase with an unpacked size of 645498 compared to 4.5.1's 644772. This slight growth could be attributed to minor code optimizations, dependency updates, or internal changes that enhance the package's overall performance or stability. Dependency updates are unespecified but probably the changes will be the update of the esbuild package, that is constantly updated in this period.
The updated releaseDate, from February 27th to March 1st, pinpoints when these changes were published, offering a timeline for developers tracking updates. For those already using Tsup, upgrading to 4.6.0 is generally recommended to leverage any improvements and stay current with the latest enhancements. When incorporating Tsup into a project, developers can expect a streamlined bundling process for TypeScript code, support for various module formats including ES modules and CommonJS, and the flexibility to configure the bundler to suit specific project requirements. Always review the package details and release notes for comprehensive insights into changes and their impact on project builds.
All the vulnerabilities related to the version 4.6.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.