Tsup 7.1.0 represents a subtle yet noteworthy upgrade over its predecessor, version 7.0.0. Both versions maintain their core purpose as zero-config TypeScript bundlers leveraging the speed of esbuild, streamlining the process for library authors. Inspecting the package data, the dependency lists of both versions have only small differences, like the release date and their sizes.
One notable change is observed in the releaseDate, where version 7.1.0 was published on June 25, 2023, signifying it incorporates the latest refinements and bug fixes up to that date, compared to version 7.0.0 released on June 16, 2023. While the core dependencies remain consistent, developers should always favour the newer version to leverage any incremental improvements or security patches introduced since the prior release.
The dist section reveals a slight size difference, where version 7.1.0 exhibits slightly larger unpackedSize of 512022 compared to 7.0.0's 511256. Such a marginal increase in size typically corresponds with added features, code optimizations, or dependency updates tucked into the newer edition.
For developers, upgrading to v7.1.0 translates into a more polished experience regarding the core bundling process. Using the newest version ensures you're building your TypeScript projects with the most recent stable toolchain, benefiting from potential performance enhancements, bug resolutions, and security improvements. While the transition from 7.0.0 should be seamless given the dependency consistency, staying current ensures a reliable and optimized build process for your libraries. For typescript library bundling, the new tsup version is a great choice.
All the vulnerabilities related to the version 7.1.0 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.