tsup version 4.12.5 introduces minimal changes compared to the preceding 4.12.4, primarily affecting package size and release timing. The unpacked size of 4.12.5 is marginally larger, 893186 bytes compared to 893185 bytes in 4.12.4, a negligible difference for most users. More significantly, version 4.12.5 was released a few hours after 4.12.4, indicating a potential hotfix or minor adjustment.
Both versions share identical dependencies, devDependencies, and peerDependencies, ensuring consistent functionality and compatibility. This includes essential tools like esbuild for fast builds, rollup for bundling, and TypeScript for type checking. Key dependencies like cac for command-line argument parsing and globby for file matching remain unchanged. The consistent peer dependency on TypeScript 4.2.3 signifies that both versions target the same TypeScript features.
Developers considering an upgrade from 4.12.4 to 4.12.5 should anticipate no breaking changes or new features. The update likely addresses a minor bug or optimization, justifying the quick turnaround in release times. The core functionality of tsup as a zero-config TypeScript bundler remains consistent, delivering efficient and streamlined builds for modern JavaScript projects. For developers experiencing specific issues in 4.12.4, upgrading to 4.12.5 is advisable, however, for others, the changes are unlikely to be impactful.
All the vulnerabilities related to the version 4.12.5 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.