Tsup version 5.11.12 is a minor update to the popular TypeScript bundler, building upon the solid foundation of version 5.11.11. Key differences primarily reside in the dependency updates, offering subtle refinements and potential performance improvements. A noteworthy change is the updated "bundle-require" dependency in version 5.11.12, jumping from 2.1.8 to version 3.0.2. This signifies a potentially crucial change in how tsup handles required bundles, which could impact the resolution and loading of dependencies within your projects. Furthermore, the "dist" section reveals an increase in unpacked size from 470192 to 472586.
For developers, this update necessitates careful consideration, especially if you're heavily reliant on custom bundle requirements. Always test your build process after upgrading to ensure seamless integration and prevent unexpected issues. While other dependencies remain largely consistent, the nuanced adjustments in core utilities like "bundle-require" can yield tangible benefits. This new relase guarantees compatibility with the newest features and fixes of dependencies which ultimately could lead to a smoother development, build and packaging experience. If your project relies on specific behaviors of the older "bundle-require" version, review the changes in version 3.0.2 to anticipate potential compatibility problems. Consider this update a good house-keeping of dependencies, improving the inner workings of tsup.
All the vulnerabilities related to the version 5.11.12 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.