Tsup version 5.2.0 introduces subtle improvements over its predecessor, version 5.1.0, continuing its focus on streamlining TypeScript project bundling. Both versions share a common core, utilizing dependencies like esbuild, rollup, and Sucrase for efficient and modern JavaScript builds. Developers familiar with Tsup will appreciate the consistent dependency landscape including cac, chalk, debug, and other essential utilities for command-line interface and utility functions, ensuring a smooth transition.
While the core functionality remains consistent, discerning users will find the subtle differences in metadata and release dates insightful. Version 5.2.0 was released on September 24, 2021, a week after version 5.1.0 which was released on September 16, 2021. Both versions maintain identical dependency and devDependency listings, from rollup-plugin-hashbang to typescript, signifying no functional changes or feature additions between these releases. The fileCount remains the same at 14 files, however, the unpackedSize gets a slight increase from 2919574 to 2921158. These values are insightful for understanding the size and distribution of the package.
For developers seeking a stable and reliable TypeScript bundler, both Tsup versions 5.1.0 and 5.2.0 offer robust solutions. The consistent dependency profiles and a short difference in release date suggest that version 5.2.0 focuses on minor internal updates or bug fixes rather than significant feature enhancements. Developers can confidently choose either version, understanding that the core bundling capabilities and developer experience should remain largely unchanged. This ensures a predictable and efficient build process for TypeScript projects, allowing developers to focus on coding rather than configuration.
All the vulnerabilities related to the version 5.2.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.