Tsup version 1.4.9 introduces subtle improvements over its predecessor, version 1.4.8, aimed at enhancing the development experience. Both versions leverage Rollup and esbuild for efficient bundling, targeting developers seeking a streamlined build process for their TypeScript projects. The core dependencies, including joycon, rollup, and rollup-plugin-esbuild, remain consistent, indicating a focus on stability in the underlying build infrastructure.
The devDependencies also mirror each other, suggesting no significant shifts in the testing or development tooling. Developers familiar with the 1.4.8 setup will find a seamless transition to 1.4.9. Key tools like typescript, prettier, and jest are still present, ensuring a robust and well-formatted codebase.The package's footprint sees a marginal increase in version 1.4.9. with the unpackedSize growing slightly to 387428 from 386820, and the fileCount going from 8 to 9, which may indicate minor additions, bug fixes, or optimization under the hood. It's worth noting that this release happened shortly after the previous, suggesting it might be a patch addressing immediate concerns within the community. For developers, this suggests that upgrading to 1.4.9 is generally safe and likely beneficial, offering subtle improvements without introducing breaking changes. However, carefully reviewing associated resources to understand the specific nature of the update remains essential before upgrading.
All the vulnerabilities related to the version 1.4.9 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.