Tsup version 3.12.0 brings several dependency updates that enhance the developer experience and improve the overall build process compared to version 3.11.0. Key dependency upgrades include rollup from version 2.34.2 to 2.38.0 providing potentially improved performance, bug fixes and new features in the core bundling process. esbuild jumps from version 0.8.16 to 0.8.34, again promising performance boosts and bug fixes, essential for fast builds. sucrase updates from 3.16.0 to 3.17.0 and @rollup/plugin-node-resolve is upgraded from 11.1.0 to the newer version. Minor updates are also present like globby moving from 11.0.1 to 11.0.2.
On the development dependencies side, the most significant change is the upgrade of Typescript from version 3.9.7 to 4.1.3 which enables developers to use new language features and leverage improved type checking. There are also minor updates to postcss and @babel/core. These updates ensure compatibility with the latest tools and standards, allowing developers to create modern, efficient builds.
The size of the unpacked package also increased slightly, from 576518 to 609408, potentially indicating the inclusion of new features or enhanced functionality. The release date also pinpoints when the upgrade happened offering more recent features. Overall these updates solidify tsup as a robust zero-config Typescript bundler optimized for modern development workflows.
All the vulnerabilities related to the version 3.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.