Tsup is a zero-config TypeScript bundler leveraging the speed of esbuild, streamlining the process of creating libraries. Comparing version 3.0.0 with the previous stable version 2.1.0 reveals several key changes beneficial for developers. While both versions aim for simplicity, version 3.0.0 introduces notable adjustments in its dependency management and bundling approach.
Notably, version 3.0.0 removes rollup-plugin-esbuild and introduces sucrase and chokidar as direct dependencies. This might signify a shift in the internal bundling strategy. The removal of kleur, pretty-bytes, @rollup/plugin-commonjs, and @rollup/plugin-node-resolve from devDependencies could suggest an optimization of the development workflow. The esbuild dependency is also updated from version 0.6.3 to 0.6.4.
Developers upgrading to version 3.0.0 should evaluate the impact of these dependency changes on their build processes. The introduction of sucrase may influence how TypeScript code is transformed during bundling. Besides the dependency bumps that usually include performance improvements and bug fixes, the usage changes can impact generated code. Also the fileCount and unpackedSize are significantly different in the two versions. Users should consider these points alongside the changes in dependencies and devDependencies when migrating to the newer tsup version.
All the vulnerabilities related to the version 3.0.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.