Tsup is a zero-config TypeScript bundler powered by esbuild, designed for creating modern JavaScript libraries. Comparing versions 4.13.0 and 4.13.1, the changes appear minimal, yet impactful for developers seeking the most up-to-date and reliable tooling. Both versions share identical dependencies, devDependencies, peerDependencies, license, repository, author, fileCount, and unpackedSize. The core bundler functionality, powered by esbuild, rollup, and supporting libraries such as sucrase, chokidar, and others, remains consistent, ensuring no breaking changes in basic usage.
The primary difference lies in the release date. Version 4.13.1 was published shortly after 4.13.0, suggesting a quick patch or minor adjustment addressing immediate issues identified in the previous release, even though the specifics are not detailed in the metadata. For developers, this implies that version 4.13.1 is likely the preferred choice due to potential (unspecified) bug fixes or optimizations.
Developers leveraging Tsup can expect a streamlined bundling experience for their TypeScript projects, benefitting from its ease of use and performance. The consistent dependencies suggest that both versions offer the same solid foundation and capabilities for bundling, making the upgrade to 4.13.1 recommended for receiving the latest possible refinements, which translates to better overall stability and reliability, even if the precise nature of those fixes remains opaque. Keep in mind that a newer version usually indicates improvements and bug fixes from the previous one.
All the vulnerabilities related to the version 4.13.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.