Tsup version 5.11.8 brings notable updates for developers seeking a streamlined TypeScript bundling experience. Comparing it to the previous 5.11.7 release, the core dependencies remain largely consistent, ensuring a stable foundation for existing projects. Key bundling tools like esbuild and rollup are held steady at versions 0.14.2 and 2.60.0 respectively, suggesting a focus on refinement rather than radical changes in the underlying compilation process.
The most apparent change lies in the updated peer dependency and dev dependency for TypeScript. Version 5.11.8 mandates TypeScript version "^4.5.4" for both peer and development environments, whereas 5.11.7 used "^4.2.3" for peer dependecy and "^4.2.4" for dev dependency. This signifies a move to leverage new TypeScript features and improvements in the latest release. While the impact depends on a project's codebase, the upgrade likely involves enhanced type checking, improved language support, and potentially better performance.
Beyond the TypeScript update, the dependency on the "source-map" package is upgraded to "^0.7.3" in version 5.11.8, which was not present in the previous release and no dependency update are shown for other used packages. This suggests a potential focus on enhancing debugging capabilities and source map generation. Developers relying on accurate source maps for comprehensive debugging in modern browsers will benefit. The fact that the updated version has an unpacked size lightly greater, hints about small features or fix addition. For developers, these changes suggest a gradual yet deliberate evolution of Tsup, emphasizing compatibility with the latest TypeScript features and refined source map handling, making tsup an even more solid solution.
All the vulnerabilities related to the version 5.11.8 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.