Tsup is a popular zero-config tool for building TypeScript libraries, designed for speed and ease of use by leveraging esbuild. Comparing versions 5.6.0 and 5.6.1, the changes appear minimal, primarily reflecting internal updates and bug fixes rather than significant feature additions. Both versions share the same core dependencies, including esbuild, rollup, sucrase, chokidar, and other essential packages for efficient bundling and code transformation. Developers can expect similar performance and functionality between the two.
The key difference lies in the releaseDate, with version 5.6.1 being released on November 12, 2021, and version 5.6.0 on November 3, 2021. Also the unpackedSize differs slightly (905738 vs 905564). This suggests that version 5.6.1 incorporates potential hotfixes or very minor tweaks addressing issues identified in the preceding version. For developers, this means that upgrading to 5.6.1 is likely a safe and recommended approach to ensure they are using the most up-to-date and stable release, benefiting from any recent bug fixes. While the dependency lists are identical, the newer version provides increased assurance of stability and reliability for TypeScript library development.
All the vulnerabilities related to the version 5.6.1 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.