Tsup version 8.2.1 introduces subtle but significant enhancements over its predecessor, version 8.2.0, aimed at streamlining the TypeScript bundling experience for developers. A key distinction lies in the dependencies, where globby has been replaced by fdir and picomatch has been introduced in 8.2.1. This suggests a refinement in how tsup handles file system operations, potentially making it more efficient or offering more granular control over file matching during bundling. The removal of colorette from the devDependencies, and the smaller package size hints at improvements in internal tooling, possibly focused on minimizing the package's footprint. Both versions maintain a robust set of core dependencies like esbuild, rollup, and sucrase, ensuring continued support for fast and efficient bundling, along with modern language features and optimizations. The peer dependencies remain consistent, requiring postcss, @swc/core, typescript, and @microsoft/api-extractor, ensuring compatibility with existing project setups and build pipelines. Developers will appreciate the continued commitment to zero-config bundling. The small differences combined suggest that 8.2.1 is a refined version with dependecy updates and internal optimizations, improving the already solid foundation established in 8.2.0, which could mean more efficient builds or a smoother experience when dealing with complex file structures. Check carefully your usage of globby, and eventual replacements for fdir and picomatch.
All the vulnerabilities related to the version 8.2.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.