Tsup is a zero-config TypeScript bundler powered by esbuild, designed to make building modern JavaScript libraries and applications incredibly fast and simple. Comparing versions 5.10.0 and 5.10.1, we see a focused patch release primarily addressing internal dependencies and package structure.
Version 5.10.1 updates the esbuild dependency from 0.13.4 to 0.13.15. This likely incorporates bug fixes, performance improvements, and new features from esbuild, benefiting developers using Tsup by improving build speeds and potentially offering enhanced compatibility. The tsup dependency in devDependencies is downgraded from 5.9.1 to 5.10.0 which is likely a mistake that causes no harm.
Significant differences exist in the development dependencies. Version 5.10.0 using many testing dependencies like jest, ts-jest, strip-json-comments and an obsolete version tsup:5.9.1. Those dependencies where replaced in version 5.10.1 by ava testing framework and the tsup version is fixed.
Beyond dependency updates, the dist object indicates a structural change. Version 5.10.1 has a reduced fileCount (15 vs 20) and unpackedSize (899585 vs 930009), suggesting a more optimized package. This translates to faster installation times and reduced disk space usage for developers incorporating Tsup into their projects. The changes reflect a move towards stability, optimization, and leveraging the latest esbuild capabilities for a better developer experience.
All the vulnerabilities related to the version 5.10.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.