Tsup version 5.12.5 is a patch release following version 5.12.4, offering incremental improvements and bug fixes for this popular zero-config TypeScript bundler. Key highlights for developers considering adopting or upgrading to 5.12.5 include potential refinements in build performance, compatibility, and stability compared to the previous version.
A notable difference lies in the adjusted devDependencies. Tsup 5.12.4 had tsup listed as a development dependency at version 5.12.2 whereas 5.12.5 lists it at 5.12.4. While this might seem unusual, it suggests internal testing or build processes might rely on specific versions of tsup itself. Furthermore, there is a difference in the vitest versions, 0.8.1 and 0.8.4 for 5.12.4 and 5.12.5 respectively. This indicates improvements or fixes in the testing suite used during development.
The dist object reveals a slight increase in the unpacked size from 475697 bytes in 5.12.4 to 475747 bytes in 5.12.5 and a more recent releaseDate. The developers probably want to upgrade to benefit from these accumulated enhancements. As a zero-config bundler, Tsup simplifies the often-complex world of module bundling, making it an attractive choice for projects seeking quick setup and reduced configuration overhead when building TypeScript libraries or applications. Keep an eye on Tsup's changelog for comprehensive details on included fixes and improvements.
All the vulnerabilities related to the version 5.12.5 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.