Tsup version 5.11.11 is a patch release following 5.11.10, offering subtle but potentially important updates for developers using this zero-config TypeScript bundler powered by esbuild. The core dependencies remain consistent, showing that the fundamental build process stays the same. Both versions use the same major versions of critical packages such as rollup, esbuild, sucrase, and chokidar.
Examining the devDependencies, the key differences emerge. Version 5.11.11 upgrades @swc/core from 1.2.124 to 1.2.126. This upgrade in the swc compiler can lead to noticeable differences in compiled code and performance. Additionally, @types/node is updated from 14.18.3 to 14.18.4 in the newer version. This potentially impacts type definitions and compatibility with newer Node.js features or APIs. Tsup 5.11.11 depends on ts-essentials version 9.1.2, while version 5.11.10 uses 7.0.3. A larger change in ts-essentials like this is very likely to include breaking version changes from interfaces requiring codebase updates. Finally, the dist object shows a slightly larger unpacked size (470192 bytes vs 470167 bytes) in the latest version, possibly due to the dependency updates. For developers, upgrading to 5.11.11 means benefiting from the latest bug fixes, performance improvements, and type definitions provided by these updated dependencies. Careful consideration should be given to testing to ensure compatibility and desired outputs are maintained.
All the vulnerabilities related to the version 5.11.11 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.