Tsup version 3.12.1 is a minor update to the popular TypeScript bundler, tsup, building upon version 3.12.0, and offering improvements and potentially bug fixes for developers seeking a zero-config TypeScript bundling solution. Both versions share a core set of dependencies crucial for seamless operation, including esbuild for blazing-fast builds, rollup for module bundling, and sucrase for faster TypeScript parsing reducing the overall bundling time.
While the primary dependencies remain consistent, slight adjustments in the devDependencies of version 3.12.1 indicate subtle enhancements for development-related tasks. Specifically, @types/node gets bumped from version 14.14.21 to 14.14.22 and fs-extra upgraded from 9.0.1 to 9.1.0 which suggests improvements in handling file system operations and possibly support for newer Node.js features during development. Additionally, the dist object reveals a slight size increase from 609408 (3.12.0) to 637246 (3.12.1) unpacked size, hinting at code additions, optimizations, or documentation updates within the bundle. For developers, upgrading to version 3.12.1 is recommended to leverage potentially improved performance, stability, and compatibility, ensuring a smoother development experience when using tsup for their TypeScript projects. The library remains focused on ease of use and rapid build times using modern tools like esbuild.
All the vulnerabilities related to the version 3.12.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.