Tsup 7.3.0 brings notable updates for TypeScript library bundling compared to version 7.2.0. Most significantly, it upgrades rollup from version 3.2.5 to 4.0.2 and esbuild from 0.18.2 to 0.19.2. These upgrades likely bring performance enhancements, bug fixes, and new features from the underlying bundlers. Developers can expect improved build times and potentially better output code. Another key change is the upgrade of rollup-plugin-dts from 5.3.0 to 6.1.0 in the devDependencies, which is crucial for generating declaration files when building TypeScript libraries, potentially bringing improved type definitions and compatibility. Also, @rollup/plugin-json get's updated from 5.0.1 to 6.0.1.
The peer dependency requirement for typescript version has also been updated from ">=4.1.0" to ">=4.5.0". Meaning older typescript version might not be compatible.
A significant shift is the removal of rollup-plugin-hashbang from the devDependencies in the newer version. This could influence how shebangs (#!/usr/bin/env node) are handled in generated output files for command-line tools. Finally, developers should note difference in the package size (unpackedSize 485920 vs 519977), potentially indicating changes in bundled files or module structure. This version incorporates newer tooling for faster and more robust TypeScript library builds, improving the developer experience and output quality.
All the vulnerabilities related to the version 7.3.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.