Tsup version 4.11.0 introduces small but impactful improvements that enhance the developer experience. Released on May 16, 2021, it builds upon the solid foundation of version 4.10.1, which came out on April 28, 2021. While the core dependencies and devDependencies remain largely consistent, certain internal improvements result in a slightly larger unpacked size of 845029 bytes compared to the previous version's 844597 bytes.
This update continues to leverage key dependencies like esbuild for fast builds, rollup for bundling, and sucrase for speedy transpilation. Developers using Tsup can expect the same reliable performance, type checking from typescript, and straightforward configuration experience. The consistent support for PostCSS with postcss-load-config remains, allowing for seamless integration with existing styling workflows. This provides confidence in keeping the existing tooling.
The core compilation experience remains consistent, which is a testament to the project's stability. The peer dependency on typescript remains at ^4.2.3, aligning with the devDependency of typescript at ^4.2.4. This means users are encouraged to have TypeScript 4.2.3 or higher installed for optimal usage, so existing codebases that already use this version can safely upgrade tsup without worrying about Typescript version compatibility. Overall, version 4.11.0 delivers a refined and reliable build environment for modern TypeScript projects, without introducing large breaking changes.
All the vulnerabilities related to the version 4.11.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.