Tsup version 4.6.1 introduces notable improvements and dependency updates compared to the previous stable version 4.6.0. One key difference lies in the updated dependencies. Specifically, Rollup is bumped from version 2.39.0 to 2.40.0 and esbuild moves from 0.8.53 to 0.8.54. Additionally, ts-jest is incremented from 26.5.1 to 26.5.2 in the devDependencies. TypeScript as a devDependency also sees an upgrade from version 4.1.5 to 4.2.2. A new dependency postcss-load-config at version ^3.0.1 has been added with version 4.6.1
These updates likely incorporate bug fixes, performance enhancements, and new features within the respective packages, contributing to a more stable and efficient development experience for users of Tsup. Developers leveraging Tsup for bundling TypeScript projects should particularly benefit from the updated Rollup and esbuild versions, potentially leading to faster build times and improved compatibility with modern JavaScript features. The upgrades in devDependencies improves developer experience, in particular for Typescript developers. The inclusion of postcss-load-config indicates enhanced support or integration with PostCSS configurations, offering increased flexibility in handling CSS processing within Tsup-powered projects. Moreover, the releaseDate indicates a very recent update, making this version a relevant choice for developers aiming to stay current with the latest improvements and features.
All the vulnerabilities related to the version 4.6.1 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.