Tsup version 6.1.3 is a patch release following closely on the heels of version 6.1.2, offering subtle improvements and bug fixes for developers leveraging this zero-config TypeScript bundler. The core functionalities remain consistent, powered by esbuild and focused on simplicity and speed in creating optimized bundles for libraries and applications, with support for various formats like ES modules, CommonJS, and IIFE, ideal for modern JavaScript development.
A notable, albeit small, change is reflected in the dist object. While both versions have the same fileCount of 16, the unpackedSize of 6.1.3 is slightly larger at 474005 bytes compared to 473969 bytes in 6.1.2. This difference hints at internal adjustments, potentially including updated dependencies or minor code modifications. Furthermore, the releaseDate indicates that version 6.1.3 was published on July 2nd, 2022, signifying a recent update addressing potential issues or incorporating minor enhancements since the release of 6.1.2 on June 10th, 2022.
Developers already using tsup will find a smooth transition, as the core configuration and usage patterns will remain familiar. It's designed for effortless setup, allowing developers to focus on writing code rather than wrestling with complex bundling configurations. Potential upgrade benefits include stability improvements and refined performance from the more recent version. For developers building TypeScript-based libraries or applications needing a fast, zero-config bundling solution, Tsup continues to be a great choice.
All the vulnerabilities related to the version 6.1.3 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.