Tsup is a zero-config bundler powered by Rollup and esbuild, designed for creating modern JavaScript libraries. Comparing versions 1.4.16 and 1.4.15, the primary difference lies in the updated dependencies. Version 1.4.16 upgrades rollup from version 2.10.0 to 2.10.3 and colorette from version 1.1.0 to 1.2.0. While the upgrade to rollup is a patch, the minor release updates may include bug fixes, performance improvements, or new features to the core bundling process, potentially influencing build times and output. Colorette v1.2.0 brings enhancements to terminal styling, which might affect the developer experience when using the CLI or viewing build logs. The file size went from 336101 to 336090. Developers considering tsup should note its reliance on Rollup and esbuild's speed for efficient bundling, especially for TypeScript projects, which is a key selling point. It simplifies the configuration process compared to directly using Rollup, allowing developers to focus more on writing code instead of wrestling with complex build setups. These updates ensure compatibility and incorporate the latest improvements from its core dependencies for an overall better user experience in terms of performance and stability.
All the vulnerabilities related to the version 1.4.16 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.