Tsup version 1.4.12 represents a minor update over the previous stable version 1.4.11, primarily focusing on refined dependency management. A key distinction lies in the addition of rollup-plugin-dts as a direct dependency in 1.4.12 at version ^1.4.6. In contrast, version 1.4.11 listed an older version 1.4.4 of the same plugin as a dev dependency. This shift suggests a potential change in how declaration files are handled within the build process, possibly streamlining type definition generation for TypeScript projects. This likely translates to a more robust and reliable experience for developers aiming to create type-safe libraries.
Another notable change is the reduced size of the package by about 50KB, possibly due to more efficient packaging or the aforementioned change.
Developers already using Tsup will want to consider the updated rollup-plugin-dts version and its potential impact on their existing build configurations. The update likely offers incremental improvements and bug fixes related to declaration generation, reinforcing Tsup's role as a convenient tool for building modern JavaScript and TypeScript libraries with esbuild and Rollup. Users should review changelogs or migration guides (if available) for any specific adjustments needed when upgrading. Overall, this release delivers enhanced stability and type definition handling for a better developer experience.
All the vulnerabilities related to the version 1.4.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.