Tsup version 4.12.4, released shortly after 4.12.3, is a minor update to this popular zero-config TypeScript bundler powered by esbuild. Both versions share the same core dependencies like esbuild, rollup, and sucrase, crucial for fast and efficient code transformation and bundling. They also maintain identical development dependencies, including testing frameworks like jest, pre-processors such as buble and svelte, and tooling for TypeScript support such as @babel/core and ts-jest.
The key difference between the two versions lies in the dist section. While both packages have a fileCount of 17, version 4.12.4 has a slightly larger unpacked size of 893185 bytes compared to 893170 bytes in version 4.12.3. This suggests a minor code change or asset update within the package. Version 4.12.4 was also released approximately 20 minutes after version 4.12.3. For developers, this implies the update likely addresses a small bug fix, performance tweak, or documentation improvement. Given the minimal change, upgrading from 4.12.3 to 4.12.4 is recommended for users seeking the most stable and up-to-date experience with Tsup. Because of the similar dependencies you should expect the same excellent support for modern Javascript features. If you are looking for a TypeScript bundler with no configuration then Tsup is an excelent option.
All the vulnerabilities related to the version 4.12.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.