Tsup version 1.4.4 arrives hot on the heels of 1.4.3, bringing subtle but potentially impactful enhancements to this Rollup-based ES bundler. Both versions share the core mission of simplifying the process of creating production-ready JavaScript libraries and applications. Key dependencies like joycon, rollup, and rollup-plugin-esbuild remain consistent, ensuring a stable foundation for bundling. Developers relying on these core functionalities should experience seamless continuity.
However, a noteworthy difference lies in the updated package size and release date. Version 1.4.4, released on May 14, 2020, exhibits a slightly larger unpacked size of 390276 bytes compared to 1.4.3's 389752 bytes which was published on May 13, 2020, suggesting minor internal adjustments or dependency updates. While the devDependencies remain identical, this size difference could indicate refinements in the bundling process or inclusion of additional resources.
For developers already using Tsup, the upgrade to 1.4.4 is likely safe, offering a potentially improved, albeit subtly, bundling experience. While a detailed changelog isn't available from the provided data, the small size increase makes it plausible that it consists of bug fixes or performance tweaks. Before upgrading, it is advisable to test the new version in a non-production environment. New developers should check the repository for version-specific information not available here. Because the changes appear minimal, most users probably will not notice any significant effect on their workflow.
All the vulnerabilities related to the version 1.4.4 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.