Tsup is a modern bundler that streamlines TypeScript project development, offering a fast and efficient build process. Comparing versions 5.11.3 and 5.11.2, the core functionalities remain consistent, providing developers with a zero-config TypeScript bundler powered by esbuild. Both versions leverage popular tools like Rollup, Sucrase, and Chokidar for robust bundling, transpilation, and file watching capabilities. Key features retained include support for various module formats (ESM, CJS, IIFE), code splitting, and the generation of declaration files (.d.ts) for enhanced type safety.
A subtle difference lies in the release dates and potentially minor internal adjustments. Version 5.11.3 was released shortly after 5.11.2, suggesting that it addresses some bug fixes or incremental improvements, while the core set of dependencies like esbuild, rollup, sucrase, cac and others are remaining the same between the two versions. Version 5.11.3 has a release data of "2021-12-14T08:03:06.835Z" while version 5.11.2 has a relase data of "2021-12-14T04:55:36.134Z". The unpackedSize is slightly different as well, with 5.11.3 showing 464427 and 5.11.2 presenting 464423.
For developers, Tsup offers several advantages: a simplified configuration, optimized builds, and excellent TypeScript support. Choosing between these two versions is unlikely to drastically impact most projects; however, upgrading to 5.11.3 is generally recommended to benefit from any potential bug fixes and minor enhancements. Always consult the official changelog for the most detailed breakdown of changes between versions to make the best decision for your project, making sure to upgrade to the last one for bigger security improvements.
All the vulnerabilities related to the version 5.11.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.