Tsup version 4.8.19 represents a minor update over its predecessor, 4.8.18, offering subtle yet potentially impactful refinements for developers leveraging this zero-config TypeScript bundler. While the core functionalities remain consistent, a key observable difference lies in the increased unpacked size of the distribution package, jumping from 757909 bytes in 4.8.18 to 831191 in 4.8.19. This suggests the inclusion of new features, assets, or code optimizations that contribute to a larger footprint. Although seemingly small, a major update like this brings significant improvements in performance, stability, and new functionality that can greatly improve developer experience.
Developers will find these changes improve the build process due to the integration of new modules, like consola, which weren't present in the previous version. These improvements may introduce new customization options and cater to an broadened spectrum of Typescript usage patterns. This release can lead to improved build times, better error reporting, more streamlined configuration, and enhanced compatibility with modern Javascript frameworks.
Furthermore, the updated release date signifies recent maintenance and improvements, assuring users of continued support and feature enhancements. Upgrading becomes essential for those prioritizing the most refined tooling experience, benefiting from the latest under-the-hood tweaks and additions that enhance Tsup's usability in their projects.
All the vulnerabilities related to the version 4.8.19 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.