Tsup version 6.6.0 introduces several notable updates and improvements compared to the previous stable version 6.5.0. A key enhancement lies in the updated esbuild dependency, moving from version 0.15.1 to 0.17.6. This upgrade likely brings performance improvements and new features offered by the newer esbuild release, potentially leading to faster build times and better support for modern JavaScript syntax. Another significant change is the updated bundle-require dependency, advancing from version 3.1.2 to 4.0.0, which might influence how modules are handled during bundling.
Furthermore, there’s an update to the Rollup plugin for generating TypeScript declaration files (rollup-plugin-dts), upgrading from version 5.0.0 to 5.1.0, suggesting refinements in how type definitions are created and managed. The primary TypeScript version used for development jumps from 4.6.3 to 4.9.5 exposing to new language features and bug fixes. Vitest, the testing framework is also updated from 0.21.1 to 0.28.4 including features requested by the community. The fileCount and unpackedsize of the package also increased. These updates collectively point towards a more refined and feature-rich developer experience when utilizing Tsup for bundling TypeScript libraries. Developers should review esbuild's release notes to leverage the latest advancements of version 0.17.6.
All the vulnerabilities related to the version 6.6.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.