Tsup version 5.12.0 introduces subtle yet potentially impactful refinements compared to the previous stable version, 5.11.13, making it a worthwhile upgrade for developers leveraging this zero-config TypeScript bundler. While the core dependencies remain largely consistent, including essential tools like esbuild, rollup, and sucrase for efficient code transformation and bundling, a noteworthy addition surfaces in version 5.12.0: the "source-map" dependency at version 0.7.3. This suggests an enhanced focus on debugging capabilities, potentially improving the generation and handling of source maps for easier troubleshooting during development.
Beyond this, the "dist" section reveals minor differences; version 5.12.0 has a slightly larger unpacked size (472900 bytes) compared to version 5.11.13 (472477 bytes), it could indicate small updates to internal modules within the tool. The release date also highlights a recent update, indicating ongoing maintenance and improvements. The development dependencies, peer dependencies, license, repository, and author remain consistent between the two versions, indicating a stable foundation and continued support.
For developers, upgrading to version 5.12.0 promises potentially better debugging experiences through the "source-map" update. This is especially relevant for larger projects where efficient debugging can save valuable time. It is always a good practice to test such upgrades thoroughly due to the difference in the unpacked size and release date to ensure compatibility and catch any edge cases specific to your project. Overall, tsup continues to offer a streamlined bundling experience, now with potential improvements in source map handling.
All the vulnerabilities related to the version 5.12.0 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.