Tsup is a zero-config bundler for TypeScript projects, designed for speed and simplicity. Comparing versions 5.7.4 and 5.7.3, the changes appear minor but potentially impactful. Both versions share the same core dependencies like esbuild, rollup, and sucrase for efficient bundling and code transformation. Furthermore they have the same devDependencies that provide useful utility libraries during development, testing, and building processes. The peer dependency remains typescript@^4.2.3, ensuring compatibility with a specific TypeScript version. A notable difference between the two versions is that the size of the unpacked package increased slightly from 871968 to 873243 bytes, suggesting minor code additions, documentation updates, or asset inclusions. The releaseDate also highlights a relatively quick release cycle, with version 5.7.4 being published roughly 3 hours after 5.7.3. Developers considering tsup should know it leverages modern tooling for fast builds, supports various output formats (ESM, CJS, IIFE) and offers features like code splitting and automatic externalization of dependencies. While the jump from 5.7.3 to 5.7.4 seems small, it may include bug fixes or incremental improvements that enhance the overall developer experience. Always consult the official changelog for a detailed list of modifications.
All the vulnerabilities related to the version 5.7.4 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.