Tsup is a zero-config build tool powered by Rollup and esbuild, designed for creating modern JavaScript libraries. Comparing versions 1.4.17 and 1.4.16, developers will find subtle but important differences primarily in dependency updates, showcasing the project's commitment to incorporating the latest improvements and bug fixes from its ecosystem.
Specifically, version 1.4.17 upgrades the rollup-plugin-dts dependency from version 1.4.6 to 1.4.7, and the @types/node devDependency from version 14.0.1 to 14.0.5. These upgrades often include performance enhancements, resolved issues, and potentially new features within the respective plugins, contributing to a smoother and more reliable build process when generating declaration files and working with Node.js types. The core functionality of Tsup remains consistent, providing a streamlined experience for bundling TypeScript code with features like automatic externalization of dependencies and support for various output formats.
For developers considering Tsup, these incremental updates highlight the importance of staying current with the package. While the core API remains stable, dependency updates like these can subtly influence the build process and ensure compatibility with the latest tooling and TypeScript versions. Reviewing the changelogs of the updated dependencies is recommended for detailed information on specific improvements and potential breaking changes introduced in those minor releases.
All the vulnerabilities related to the version 1.4.17 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.