Tsup version 8.1.1 arrives as a refined iteration of the popular TypeScript bundler, building upon the foundations laid by version 8.1.0. Key updates primarily target core dependencies, indicating a focus on stability and compatibility. Notably, esbuild jumps from version 0.21.4 to a much newer 0.23.0, potentially unlocking performance enhancements and access to the latest esbuild features. Sucrase also sees a significant update, indicating improvements in JavaScript/TypeScript processing. Dependency upgrades like rollup and consola likely introduce bug fixes and minor improvements. The peer dependencies remain consistent, ensuring compatibility with existing projects using specified versions of PostCSS, SWC core, TypeScript, and Microsoft API Extractor. For developers, this translates to a more reliable build process and access to newer features through the updated dependencies. Specifically, the upgrade of @microsoft/api-extractor and typescript in the devDependencies ensures a more robust type-checking and API documentation generation experience for library authors. While the core functionality of Tsup remains the same, these dependency bumps address underlying issues, potentially optimizing build times and overall project health.
All the vulnerabilities related to the version 8.1.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.