Tsup is a build tool that leverages Rollup and ESBuild to bundle TypeScript code. Comparing versions 1.4.6 and 1.4.5, the core functionality remains consistent, indicating a maintainable and stable tool for developers. Both versions share the same dependencies, including joycon for configuration, rollup for bundling, and rollup-plugin-esbuild for fast TypeScript compilation. The developer dependencies also remain identical, suggesting that the internal tooling and testing setup have not changed between these minor releases. These shared dependencies provide features for command-line argument parsing (cac), testing (jest, ts-jest), file system manipulation (fs-extra), code formatting (prettier), and type checking (typescript).
The key distinction lies in the dist metadata, specifically the unpackedSize. Version 1.4.6 has an unpacked size of 384889 bytes, slightly larger than version 1.4.5's 384723 bytes. This small increase is likely due to minor code adjustments, potentially bug fixes, or documentation updates. For developers, this suggests a focus on stability and incremental improvements rather than major feature additions. The timestamps provided in releaseDate indicates a release interval of about 11 minutes, indicating a very fast turnaround in releasing fixes or small changes. While the core functionality remains stable, users should always review changelogs (if available) to identify the specific changes that contribute to the slight size difference. The continued reliance on well-established tools like Rollup also suggests that Tsup benefits from the wider Rollup ecosystem and its plugin capabilities.
All the vulnerabilities related to the version 1.4.6 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.