Tsup version 1.4.14 represents a minor update over the previous stable version 1.4.13, focusing primarily on internal improvements and bug fixes rather than introducing new features. Both versions center around leveraging Rollup and esbuild for blazing-fast JavaScript and TypeScript bundling. The core dependencies, including joycon, rollup, rollup-plugin-dts, and rollup-plugin-esbuild, remain consistent, ensuring the core functionality and build pipeline remain stable. Similarly, developer tooling such as cac, jest, ts-jest, prettier, and various @rollup/plugin-* packages remain unchanged, simplifying the upgrade process. The most visible change lies in the dist object, specifically the unpackedSize, which has increased slightly from 335581 bytes in 1.4.13 to 335886 bytes in 1.4.14. This suggests subtle modifications within the packaged code, potentially related to optimized code paths or minor adjustments to internal modules. The releaseDate also reflects these changes, with version 1.4.14 being published later on the same day as 1.4.13, indicating a quick follow-up release. For developers already using Tsup, upgrading from 1.4.13 to 1.4.14 should be a seamless process, providing a slightly optimized and potentially more stable experience without requiring any code changes. While no groundbreaking features are present, the incremental improvements contribute to a more robust build process.
All the vulnerabilities related to the version 1.4.14 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.