Tsup version 1.4.5 introduces subtle yet important updates for developers leveraging its capabilities to bundle TypeScript and ESNext code. Comparing it to the previous stable version, 1.4.4, reveals that while the core dependencies like joycon, rollup, and rollup-plugin-esbuild remain consistent, the development dependencies have seen updates. Most notably, cac has been bumped from version 6.5.8 to 6.5.9, @types/jest from 25.2.1 to 25.2.2 and @types/node from 13.9.2 to 14.0.1. These upgrades likely incorporate bug fixes or minor feature enhancements within these tools, potentially leading to a smoother development experience.
Furthermore, examining the dist section indicates a slight decrease in unpackedSize from 390276 bytes in 1.4.4 to 384723 bytes in 1.4.5, hinting at possible optimizations in the bundled output. The release dates also show a narrow time gap, both published on same day, meaning that the newer version contains some hotfixes. For developers already using Tsup, upgrading to 1.4.5 could bring marginal improvements in build performance or stability due to underlying dependency updates and size optimisation. However, the change is not so substantial as to introduce breaking changes for existing configurations.
All the vulnerabilities related to the version 1.4.5 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.