Tsup version 5.10.3 is a minor release following 5.10.2, both versions primarily focusing on bundling TypeScript code. Comparing the two, there are subtle differences in their distribution packages. Version 5.10.3 has a slightly smaller unpacked size (903927 bytes vs 904334 bytes) and fewer files in the tarball (16 vs 21) which might indicate some optimization or refactoring in how the package is structured.
Both versions share identical dependencies and devDependencies, crucial for developers using Tsup. Key dependencies include esbuild and rollup, highlighting Tsup's ability to leverage different bundlers. The presence of sucrase indicates support for faster development builds by offering an alternative to the full TypeScript compiler. Essential devDependencies like typescript, @swc/core ,and @babel/core show the diverse ecosystem Tsup integrates with for testing and development.
Developers interested in using Tsup should note that both releases require TypeScript version ^4.2.3 as a peer dependency. This ensures compatibility and proper functioning. Overall, the transition from 5.10.2 to 5.10.3 appears to be a refinement, potentially improving package size and structure without introducing major feature changes or dependency updates. Developers can likely upgrade seamlessly, benefiting from subtle improvements.
All the vulnerabilities related to the version 5.10.3 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.