Tsup version 5.7.2 is a minor release following 5.7.1, primarily focusing on internal improvements and potential bug fixes, as indicated by the small version bump. Both versions share the same core dependencies, including popular tools like esbuild, rollup, and Sucrase for efficient code bundling and transformation. They also rely on utilities like cac for command-line argument parsing and chalk for enhancing console output. Key development dependencies like TypeScript, Jest, and Prettier remain consistent, suggesting a stable development environment.
The crucial difference lies in the dist section: version 5.7.2 has a slightly reduced unpacked size (871857 bytes) compared to 5.7.1 (905945 bytes). This suggests optimizations or the removal of unnecessary files in the newer version, leading to a smaller distribution footprint. While both versions offer the same core functionality for developers seeking a zero-config TypeScript bundler, the newer 5.7.2 may present a slightly leaner and more efficient package. Both versions maintains typescript version ^4.2.3 as peer dependency.
For developers, Tsup provides a streamlined bundling experience, handling TypeScript compilation, tree-shaking, and code splitting with minimal configuration. This makes it an excellent choice for both library and application development. The consistent dependency versions across these releases indicate a focus on stability and maintaining compatibility with existing projects. The update is recent, as the release date of 5.7.2 is less than 24 hours after the previous version.
All the vulnerabilities related to the version 5.7.2 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.