Version 4.3.24 of @umijs/bundler-esbuild represents a minor update over the previous stable version, 4.3.23, primarily focused on internal improvements and dependency updates. The core functionality of the bundler remains consistent, offering developers a performant build tool leveraging esbuild for the UmiJS framework. Both versions share the same core dependencies including postcss for CSS processing, @umijs/utils and @umijs/bundler-utils for internal utilities, enhanced-resolve for module resolution, postcss-preset-env for modern CSS features, and postcss-flexbugs-fixes to address common flexbox issues. The development dependency on @alitajs/postcss-plugin-px2rem for converting pixels to rem units also remains unchanged, suggesting a continued emphasis on responsive design support.
The key difference lies in the @umijs/utils and @umijs/bundler-utils dependencies which are updated to version 4.3.24 from 4.3.23. Without further context, these changes likely involve bug fixes, performance enhancements, or minor feature additions within UmiJS's internal utility functions that directly impact the bundler's operation. The releaseDate indicates a recent update providing latest fixes. For developers already using @umijs/bundler-esbuild, upgrading from 4.3.23 to 4.3.24 is recommended to benefit from these underlying improvements and ensure compatibility with the broader UmiJS ecosystem. Developers integrating the bundler for the first time should opt for the latest version (4.3.24) to start with the most up-to-date and optimized codebase.
All the vulnerabilities related to the version 4.3.24 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.