Tsup is a tool that leverages Rollup and esbuild to streamline the bundling process for JavaScript and TypeScript projects. Comparing versions 1.4.8 and 1.4.7 reveals subtle but potentially beneficial differences for developers. Both versions depend on the same core libraries: joycon, rollup, and rollup-plugin-esbuild, indicating a stable foundation for bundling. The devDependencies also remain identical, suggesting that the tooling and testing environment used in the package's development hasn't changed between these versions. This consistency is reassuring for developers relying on Tsup for build processes, as it implies a low risk of breaking changes related to testing or development workflows.
The key difference lies in the build itself. The unpacked size of version 1.4.8 is slightly larger (386820 bytes) compared to 1.4.7 (386580 bytes). This suggests that bug fixes, performance improvements, or small feature enhancements have been incorporated. Crucially, the file count remains the same at 8, hinting that the core structure of the package hasn't been radically altered. The release times also tell a story: version 1.4.8 followed 1.4.7 very closely on the same day, implying a quick patch release or minor update. While the specific changes aren't detailed in these package manifests, upgrading to 1.4.8 is likely a safe bet to benefit from the latest refinements without significant disruption, especially for those seeking the most up-to-date and potentially optimized bundling experience.
All the vulnerabilities related to the version 1.4.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.