Tsup version 4.9.0 introduces several notable updates compared to the previous stable release, 4.8.21, making it an attractive option for developers seeking enhanced build tooling. Key dependency upgrades include esbuild which jumps from version 0.10.2 to 0.11.12, offering improved performance and potentially new features in the Javascript and Typescript build process. Rollup is also updated to version 2.45.2 from 2.41.2 which might ship with a set of new features and bug fixes. Globby sees a minor version bump from 11.0.2 to 11.0.3.
On the development dependency side, several packages also receive updates. Svelte is updated to 3.37.0 and Typescript becomes 4.2.4 and Postcss becomes 8.2.10. Crucially, @types/node moves from version 14.14.35 to 14.14.41, and @types/fs-extra jumps from 9.0.8 to 9.0.11 and @babel/core goes to 7.13.15. While these might seem minor, these crucial updates enhance type safety and integration with the latest Node.js features and filesystem functionalities, benefiting the overall development experience.
Developers should also take note of this new version, because the size of the packaged has increased as they can see from the unpackedSize property (840909 from 837237), so it might be important to test it. The new release also comes out almost a month after the previous stable so, if important bugs were in place, they should be fixed.
All the vulnerabilities related to the version 4.9.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.