Tsup is a zero-config TypeScript bundler powered by esbuild, designed for creating highly optimized and fast builds for libraries and applications. Version 4.7.2 brings subtle yet important updates compared to version 4.7.1. Primarily, the core Rollup dependency has been updated from version 2.40.0 to 2.41.2. While seemingly minor, this Rollup update may bring performance improvements, bug fixes, and potentially new features within the bundler itself. Furthermore, developers using PostCSS will notice a minor update from version 8.2.7 to 8.2.8. This suggests a small patch or enhancement in PostCSS integration, which could influence styling workflows for projects leveraging Tsup. Another crucial change lies within the @babel/core dev dependency, moving from version 7.13.8 to 7.13.10. This update could provide refinements in Babel transformations and compatibility. Finally there is a tiny difference in the @types/node dependency, moving from version 14.14.32 to 14.14.35.
Developers interested in Tsup should note that these incremental updates highlight the active maintenance and improvement of the tool. Upgrading from 4.7.1 to 4.7.2 ensures you are benefiting from potential performance gains, bug resolutions, and the latest advancements in the underlying libraries like Rollup and PostCSS, enabling a smoother and faster development experience when creating modern JavaScript and TypeScript projects.
All the vulnerabilities related to the version 4.7.2 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.