Tsup is a zero-config bundler that leverages esbuild to make building Javascript, Typescript and React libraries fast and easy. Comparing version 5.7.1 with its predecessor, 5.7.0, reveals a minor patch improving stability, but no major changes, new features or breaking API updates. Therefore upgrading should present minimal issues.
Both versions share a robust set of dependencies and devDependencies, including Rollup, esbuild, Sucrase, and Typescript, indicating a well-established toolchain for bundling and transpilation. They each depend on a similar set of utilities like cac for command-line argument parsing, chalk for colored terminal output, and debug for debugging, highlighting the project's focus on developer experience. Development dependencies include testing frameworks, pre-processors, and utilities for a modern development setup like Jest, Prettier, rollup-plugin-dts for .d.ts files and more.
The core bundling functionality remains consistent. While both versions use identical dependency and devDependency versions, the patch from 5.7.0 to 5.7.1 suggests a subtle internal update focused on bug fixes or performance improvements rather than introducing new functionalities. Developers can expect similar features and performance characteristics between these versions, making the transition straightforward.
All the vulnerabilities related to the version 5.7.1 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.