Tsup is a zero-config Typescript bundler powered by esbuild, designed for creating modern JavaScript libraries. Version 4.8.11 represents a subtle yet potentially significant iteration over its predecessor, version 4.8.10. While both versions share core dependencies and dev-dependencies, the crucial difference lies in the "dist" section, specifically the "unpackedSize". Version 4.8.11 possesses an unpacked size of 756698 bytes, a minor increase from version 4.8.10's unpacked size of 756618 bytes.
This difference, although numerically small, suggests internal changes, possibly bug fixes, performance tweaks, or updated build artifacts that do not necessitate changes to code itself. Both versions come equipped with tools useful to web-developers, like the possibility to bundle Typescript. The libraries included, like esbuild and rollup suggest great performance. The sucrase library helps on stripping Typescript annotations for faster performance.
For developers using Tsup, upgrading to version 4.8.11 is recommended to benefit from these incremental improvements, even without a detailed changelog highlighting substantial feature additions or API modifications. Consider using this library to improve your bundling flow from Typescript. Ensure that tooling dependencies are up-to-date while upgrading between these versions. The release dates (both in March 2021) show an active cadence for feature improvements.
All the vulnerabilities related to the version 4.8.11 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.