The npm package tsup version 1.0.0 marks a significant milestone in the evolution of this bundler, built upon Rollup and ESBuild, designed to simplify the process of creating modern JavaScript libraries and applications. This release introduces several key dependencies and devDependencies that enhance the developer experience and improve the tool's capabilities compared to its previous stable version (information unavailable).
Notably, tsup 1.0.0 relies heavily on Rollup (version ^2.8.2) and rollup-plugin-esbuild (version ^1.3.1) for its core bundling functionality. This combination promises both speed and efficiency in transforming your TypeScript or JavaScript code into optimized bundles. The inclusion of devDependencies like cac (command-line argument parser), resolve (module resolution), colorette (terminal styling), and @rollup/plugin-commonjs suggest a focus on improving the CLI experience and overall project build process. The specified versions of TypeScript and its related type definitions (@types/node, @types/resolve) ensure compatibility with current workflows. Also important is the inclusion of rollup-plugin-hashbang that allows adding hashbang to the output files, really important for CLI tools.
For developers, upgrading to version 1.0.0 could unlock faster build times and a smoother development workflow. The addition of styling through colorette seems focused to create a more informative command line interface when working with CLI. Its clear with the given information that tsup is perfect for bundling modern JavaScript projects.
All the vulnerabilities related to the version 1.0.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.