Tsup version 5.0.0 represents an evolution from the previous stable release, 4.14.0, offering developers refined tooling for streamlined TypeScript project bundling. Key dependency updates and additions mark the transition. Most notably, esbuild was updated from version 0.12.9 to 0.12.28. The removal of the sucrase dependency from the dependencies list and the addition of strip-json-comments as a development dependency is one more notable diference.
Both versions share core dependencies such as rollup, esbuild, cac, and chalk, vital for their bundling and command-line interface capabilities. These ensure that consistent functionality is maintained. The peer dependency on typescript remains at ^4.2.3, suggesting minimal breaking changes related to TypeScript language features.
While both versions offer similar core functionalities for building modern JavaScript libraries, version 5.0.0 incorporates incremental improvements that could lead to enhanced build performance and potentially offer newer features or bug fixes through its updated dependencies. Developers should evaluate the impact of esbuild and the removal sucrase and the new addition strip-json-comments. Examining the changelog of esbuild between versions 0.12.9 and 0.12.28 should reveal essential fixes, performance tweaks, or expanded capabilities that might influence your build processes.
All the vulnerabilities related to the version 5.0.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.