Tsup version 8.3.0 arrives as a fresh update, released on September 17, 2024, following closely behind version 8.2.4, released in early August of the same year. Both versions continue to provide a zero-config TypeScript bundler powered by esbuild, streamlining the development process for library creation. However, a key change lies in the dependencies. While both share a majority of the same dependencies, version 8.3.0 replaces globby with tinyglobby. tinyglobby is known for speed and efficient pattern matching, suggesting a focus on improved performance for file discovery and bundle creation in the new version. The unpacked size shows a small increase from 437007 to 437302, indicating slight adjustments in the bundled code or assets. For developers, the updated version implies faster build times due to the switch in globbing libraries.
Both versions consistently support key peer dependencies like PostCSS, SWC core, TypeScript, and Microsoft API Extractor, ensuring compatibility with common toolchains and development environments. Developers who value build speed and incremental performance improvements should consider upgrading to version 8.3.0 to leverage the benefits of the tinyglobby library. Ultimately, the update emphasizes Tsup's commitment to continuous optimization.
All the vulnerabilities related to the version 8.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.