Tsup version 3.6.0 is a patch release following version 3.5.0, both aiming to simplify TypeScript project bundling. Examining the package data, the core dependencies remain consistent between the two versions. Key dependencies like rollup for bundling, esbuild for fast builds, and sucrase for alternative TypeScript compilation stay at the same versions. Similarly, development dependencies used for testing and development, such as jest, typescript, and various @types/* packages, are unchanged, suggesting a focus on internal improvements rather than major feature additions.
The dist section reveals slight differences: version 3.6.0 has a marginally larger unpacked size (687339 bytes) compared to 3.5.0 (686757 bytes). This difference is small but may indicate minor code additions or changes to the bundled output. The release dates show version 3.6.0 was published shortly after version 3.5.0, indicating a quick patch addressing potential issues. Developers can likely upgrade confidently to 3.6.0, anticipating no breaking changes and benefiting from stability improvements and any minor fixes. The unchanged dependency versions suggest a low-risk upgrade focused on refinement. It is recommended to check the changelog for more detailed information about what was patched or improved on version 3.6.0.
All the vulnerabilities related to the version 3.6.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.