@umijs/bundler-esbuild versions 4.3.16 and 4.3.17 are both bundlers leveraging esbuild for the UmiJS framework, designed to provide fast and efficient builds for web applications. Examining the differences between these two releases, the core functionality remains consistent, but subtle dependency updates and internal improvements likely contribute to enhanced stability and performance. The most notable difference lies in the dependencies: @umijs/utils and @umijs/bundler-utils. Version 4.3.17 depends on @umijs/utils@4.3.17 and @umijs/bundler-utils@4.3.17, while version 4.3.16 depends on @umijs/utils@4.3.16 and @umijs/bundler-utils@4.3.16. This suggests that upgrading from 4.3.16 to 4.3.17 will probably include fixes and new features in these 2 packages, improving workflow of developers, although it may not be documented since only the patch number has changed. Both versions depend on the same set of core dependencies, this means that you should not encounter any differences in the supported PostCSS, enhanced-resolve, postcss-preset-env versions. The packages also have the same "fileCount" and "unpackedSize", meaning that the changes are probably located inside the previous dependencies and not in the current one. Crucially, developers should note the releaseDate. Version 4.3.17 was released more recently than 4.3.16, hinting that it incorporates the very latest fixes and optimizations. Upgrading to the newest patch version is generally recommended. These updates are important for seamless integration within the UmiJS ecosystem.
All the vulnerabilities related to the version 4.3.17 of the package
fast-redact vulnerable to prototype pollution
fast-redact is a package that provides do very fast object redaction. A Prototype Pollution vulnerability in the nestedRestore function of fast-redact version 3.5.0 and before allows attackers to inject properties on Object.prototype via supplying a crafted payload, causing denial of service (DoS) as the minimum consequence.
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.