Tsup, the Rollup-based bundler leveraging esbuild's speed, saw a minor version bump from 1.4.14 to 1.4.15 on May 18, 2020. Both versions share the same core dependencies: joycon for configuration management, rollup for bundling, rollup-plugin-dts for generating declaration files, and rollup-plugin-esbuild for the fast transformation of TypeScript and JavaScript code.
The developer dependencies also remain consistent, including testing frameworks like Jest and ts-jest, command-line argument parsing with cac, tools for execution (execa), module resolution (resolve), file system operations (fs-extra), code formatting with prettier and others. TypeScript and its related type definitions are present for development purposes.
The primary distinction lies in the dist object. While both versions contain 8 files in the packaged tarball, version 1.4.15 has a slightly larger unpacked size of 336101 bytes, compared to 335886 bytes in 1.4.14. The releases were also very close in time. Developers considering an upgrade should investigate the delta contributing to this size difference. It could encompass bug fixes, performance enhancements, or the inclusion of new assets. For existing users, a changelog or detailed release notes (beyond the package manifest) would offer a better understanding of the precise changes introduced by this update. While seemingly small, such updates might deliver valuable benefits for build performance or stability.
All the vulnerabilities related to the version 1.4.15 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.