Tsup, a zero-config TypeScript bundler powered by esbuild, released version 4.10.0, building on the solid foundation of version 4.9.2. Both versions share a core set of dependencies aimed at efficient bundling, including esbuild, rollup, sucrase, and utilities like cac, chalk, and debug. Key development dependencies remain consistent as well, such as typescript, jest, prettier, and various @types/* packages, ensuring a smooth development experience with testing, formatting, and type safety.
While the dependency lists appear largely unchanged, a notable difference lies in the dist metadata. Version 4.10.0 boasts a file count of 16 and an unpacked size of 844424 bytes, compared to version 4.9.2's file count of 10 and unpacked size of 840815 bytes. This suggests that version 4.10.0 might include some added features, enhanced documentation, or internal restructuring leading to the slightly larger distribution size and more files.
Developers considering upgrading to 4.10.0 should be aware of this difference in size, though the minimal increase likely won't be a detriment. The focus for upgrades should be on any bug fixes, performance improvements, or new capabilities that may have been introduced. Without detailed changelogs, verifying and testing integration is paramount. Both 4.9.2 and 4.10.0 rely on peer dependency typescript":"^4.2.3". Use these versions when working with compatible typescript compilation.
All the vulnerabilities related to the version 4.10.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.