Tsup is a zero-config tool for building TypeScript libraries, designed for simplicity and speed. Comparing versions 5.12.3 and 5.12.2, the primary difference lies in the updated tsup dependency within the devDependencies of version 5.12.3, which now points to version 5.12.2, while the previous version had tsup at 5.11.10. It signals internal testing or integration with the immediate prior release. Both versions share a consistent set of core dependencies crucial for their functionality, including esbuild for fast bundling, rollup for module packaging, and sucrase for faster TypeScript compilation. The devDependencies reveal the tooling ecosystem tsup utilizes for development and testing, incorporating libraries like vitest for unit testing, prettier for code formatting, and various @types/* packages for type safety. Also they both have the same peer dependency, typescript version ^4.1.0.
Version 5.12.3 was released on April 2, 2022, a little after 5.12.2, reflecting ongoing improvements and stability enhancements. The small change in file size and unpacked size hints at incremental adjustments rather than major architectural shifts. For developers, tsup minimizes configuration overhead, streamlining the build process for TypeScript projects. Its dependency on performant tools like esbuild ensures rapid build times, making it an attractive choice for projects prioritizing speed and efficiency in their development workflow. The consistent dependency structure between the two version highlights a stable core, while the minor updates suggest continuous refinement and a focus on developer experience.
All the vulnerabilities related to the version 5.12.3 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.