tsup version 6.4.0 brings several notable updates compared to version 6.3.0, impacting developers building TypeScript libraries. A key change lies in the updated rollup dependency, advancing from version 2.74.1 to 3.2.5. This upgrade unlocks newer features and potential performance improvements within Rollup, the underlying bundler. The bundle-require dependency also sees a bump from 3.1.0 to 3.1.2. While seemingly minor, dependency updates often include bug fixes and refinements, contributing to a more stable build process.
Furthermore, version 6.4.0 introduces a new dependency: source-map at version 0.8.0-beta.0. This suggests a focus on enhanced debugging capabilities, particularly concerning source map generation and accuracy as the library embraces a pre-release version.
On the other hand, there have been some considerable updates in the related devDependencies. rollup-plugin-dts updates from 4.2.1 to 5.0.0, @rollup/plugin-json goes from 4.1.0 to 5.0.1, suggesting potentially improved support for generating declaration files and handling JSON imports in the bundled code. These improvements enhance the developer experience by streamlining library creation and usage, providing more accurate source maps, and delivering a clearer and more efficient build process. Upgrading ensures access to the latest features and bug fixes in this TypeScript bundling powerhouse.
All the vulnerabilities related to the version 6.4.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.