Tsup version 5.9.1 represents a minor update to the popular TypeScript bundler, following closely on the heels of version 5.9.0. While both versions share the same core dependencies like esbuild, rollup, and sucrase for efficient code transformation and bundling, a key difference lies in the introduction of bundle-require as a dependency in v5.9.1 and the removal of chalk. This addition likely provides enhanced module resolution capabilities and more sophisticated handling of required files within the bundling process. Developers will appreciate the improved flexibility this offers when dealing with complex project structures. Moreover, the unpacked size of version 5.9.1 is slightly larger which may indicate either the need for disk space or a greater number of functionalities provided in the new release.
Both versions support peer dependencies for TypeScript v4.2.3, ensuring compatibility with existing TypeScript projects. The development dependencies largely mirror each other, encompassing testing frameworks like jest, and code quality tools such as prettier and typescript, which facilitates project setup and maintenance. Tsup remains a zero-config TypeScript bundler designed for speed and ease of use, making it suitable for library authors and application developers seeking efficient build processes. This fast iteration cycle highlights Tsup's ongoing commitment to improve developer experience through continuous upgrades in its module resolution, bundling, dependency handling and more.
All the vulnerabilities related to the version 5.9.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.