Tsup is a zero-config TypeScript bundler powered by esbuild, designed for effortless creation of optimized JavaScript libraries. Versions 4.8.17 and 4.8.16 are closely related, offering developers a streamlined build process that minimizes configuration overhead. Both versions share identical dependencies and development dependencies, ensuring a consistent toolchain for TypeScript projects. Key dependencies include esbuild for lightning-fast bundling, Rollup for plugin-based transformations, and Sucrase for non-standard syntax support. Development tools encompass testing frameworks like Jest, formatters like Prettier, and essential TypeScript definitions. The peer dependency on TypeScript ensures compatibility with existing TypeScript projects.
The sole difference between the two versions lies in the dist object. Version 4.8.17 has a slightly larger unpackedSize (757650 bytes) compared to version 4.8.16 (757333 bytes), and a later releaseDate. This suggests that version 4.8.17 contained very minor bug fixes and/or improvements, which resulted in a slightly bigger package size, and therefore is better suited than the prior version.
For developers seeking rapid TypeScript library development, Tsup provides a valuable solution and even if the difference is minimal, 4.8.17 is the preferred one because it represents a newer version with the latest set of bug fixes. Its zero-config approach drastically reduces setup time, and allows developers to focus primarily on the code itself.
All the vulnerabilities related to the version 4.8.17 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.