Tsup version 4.7.0 marks an incremental update over the previous stable release, version 4.6.1, offering developers a refined experience in bundling TypeScript libraries. While the core functionality remains consistent, key differences lie in the updated dependency versions, reflecting the ongoing enhancements in the JavaScript ecosystem.
Specifically, esbuild moves from version 0.8.54 to 0.9.2, potentially bringing performance improvements and new features. Users should refer to esbuild's changelog for detailed information. The crucial TypeScript peer dependency shifts from version 4.2.2 to 4.2.3, ensuring compatibility with the latest TypeScript features and bug fixes, which is important for projects leveraging modern TypeScript syntax. Development dependencies also see updates: PostCSS is updated from 8.2.6 to 8.2.7, and ts-jest moves from 26.5.2 to 26.5.3. The most significant changes is the update of the @types/node package, which changes from 14.14.31 to 14.14.32. Svelte also moves from 3.34.0 to 3.35.0.
For developers using Tsup, these updates translate to potentially improved build times, better compatibility with the latest tools, and enhanced stability. While the changes are not revolutionary, they showcase Tsup's commitment to staying current with the evolving landscape of JavaScript development. Thoroughly reviewing the dependency updates' changelogs is recommended to understand the specific nuances and advantages they introduce to the development workflow. The file size also decreased slightly from 721444 to 720973.
All the vulnerabilities related to the version 4.7.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.