Tsup is a modern bundler specifically designed for TypeScript projects, streamlining the development process with its zero-configuration approach. Comparing versions 4.8.14 and 4.8.15, the core functionality remains consistent, focusing on fast and efficient bundling. The primary distinction lies in the bug fixes and internal improvements incorporated in the newer 4.8.15 version, reflected in its slightly larger "unpackedSize" suggesting minor code adjustments and potential enhanced stability. Developers benefit from Tsup's speed (powered by esbuild) in reducing build times, and its out-of-the-box TypeScript support simplifying setup.
Both versions boast a robust set of features including automatic externalization of dependencies(reducing bundle size), various output formats (ESM, CJS, IIFE), and code splitting, catering to diverse project needs. The inclusion of rollup-plugin-dts enables automatic declaration file generation, crucial for library authors. Tsup's dependency and devDependency lists reveal its reliance on well-established tools like Rollup, esbuild for bundling, Sucrase for faster JavaScript compilation, and Chokidar for file watching. The peer dependency on TypeScript highlights its tight integration with the TypeScript ecosystem. Overall, Tsup provides a convenient and performant solution for bundling TypeScript projects, with version 4.8.15 representing a refined iteration over 4.8.14 thanks to improvements and bug fixes, making it a preferable choice for new projects.
All the vulnerabilities related to the version 4.8.15 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.