Tsup version 3.4.3 brings several updates crucial for developers using this zero-config TypeScript bundler powered by esbuild. Comparing it to the previous version, 3.4.2, a key change lies in the updated dependencies. Most notably, esbuild jumps from version 0.6.6 to 0.6.19, potentially bringing performance improvements and bug fixes inherent in that version jump. Rollup, another core dependency, is updated from version 2.22.1 to 2.23.1, likely providing enhanced module bundling capabilities. Similarly chokidar, a file watching tool, gets bumped up from 3.4.1 to 3.4.2, so likely bug fixes and performance benefits.
On the development dependencies side, jest is upgraded from 26.1.0 to 26.3.0 and ts-jest from 26.1.3 to 26.1.4, enhancing testing capabilities. The @types/jest definition also receives an update, moving from 26.0.5 to 26.0.9. and @types/node moves from 14.0.23 to 14.0.27. These upgrades enhance type safety and provide access to newer testing features. While other dev dependencies remain consistent, the cumulative impact of these dependency updates suggests a focus on stability, performance, and enhanced testing workflows. Users are encouraged to upgrade to leverage these improvements for a smoother development experience with Tsup. The increase in unpacked size, albeit minimal, from 685346 to 685665 hints at internal changes within the bundled output.
All the vulnerabilities related to the version 3.4.3 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.