Tsup is a zero-config TypeScript bundler powered by esbuild, designed to simplify the process of packaging TypeScript libraries. Comparing versions 8.0.2 and 8.0.1, developers will find a few key differences that make the newer version potentially more appealing. While the core dependencies and functionalities remain largely consistent – including essential tools like esbuild, rollup, and sucrase for efficient bundling and transformation – the update addresses some under-the-hood aspects.
One significant modification is reflected in the release date, with version 8.0.2 being released more recently (February 10, 2024) than version 8.0.1 (November 21, 2023). This suggests that 8.0.2 may contain bug fixes, performance improvements, or minor updates not present in the older version. Also the unpackedSize value suggests different content as well even if the fileCount is the same. Both versions share the same peer dependencies, ensuring compatibility with common tools like postcss, @swc/core, and typescript . For developers, especially those working on modern TypeScript projects and wanting a streamlined bundling experience, using the latest version is generally advisable. The newer version offers the most up-to-date features and fixes which is very important for the TypeScript ecosystem.
All the vulnerabilities related to the version 8.0.2 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.