Tsup version 4.5.1 is a minimal patch update to the popular zero-config TypeScript bundler, building upon the foundation laid by version 4.5.0. Both versions share the same core set of dependencies and devDependencies, indicating a focus on stability and incremental improvements rather than radical changes. Key dependencies include esbuild for incredibly fast builds, rollup for bundling, and sucrase for speedy non-type-checking TypeScript transforms. Developers already using tsup will appreciate the familiar landscape, making the upgrade smooth.
The most notable difference between versions 4.5.0 and 4.5.1 lies in the releaseDate and slightly different unpackedSize. This strongly suggests that 4.5.1 is a bug fix or a minor adjustment release with bug fixes that addresses small issues present in 4.5.0, optimized the package published size or improves overall stability. While the functional capabilities are likely identical, adopting 4.5.1 ensures you benefit from the latest refinements and are running the most stable iteration.
For developers considering tsup, both versions highlight its strengths: ease of use, leveraging powerful tools, and a commitment to staying current with the evolving JavaScript/TypeScript ecosystem. The presence of development dependencies like jest indicates a focus on code quality and testing, further solidifying tsup's reputation as a reliable choice for bundling TypeScript projects, now with bug fixes included in the fix version.
All the vulnerabilities related to the version 4.5.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.