@umijs/bundler-esbuild is a crucial part of the UmiJS ecosystem, responsible for efficiently bundling your code for production. Comparing versions 4.3.28 and 4.3.27, the primary difference lies in the updated dependencies on other UmiJS packages and the release date. Version 4.3.28 depends on @umijs/utils v4.3.28 and @umijs/bundler-utils v4.3.28, while version 4.3.27 depends on their respective 4.3.27 counterparts. Notably, the core bundler dependencies like postcss, enhanced-resolve, postcss-preset-env, and postcss-flexbugs-fixes, along with the development dependency @alitajs/postcss-plugin-px2rem, remain consistent between the two versions. This suggests that the updates primarily involve internal UmiJS utilities and bundler utilities, likely incorporating bug fixes, performance improvements, or feature enhancements within the broader UmiJS framework. Developers leveraging @umijs/bundler-esbuild should upgrade to the latest version (4.3.28 at the time of this data) to benefit from the most recent improvements within the UmiJS ecosystem. While the core bundling functionality likely remains stable, staying current ensures optimal compatibility and performance within UmiJS projects, addressing any potential issues resolved in the dependent @umijs/utils and @umijs/bundler-utils packages. The unchanged file count and unpacked size indicate that the update is concentrated on internal code adjustments rather than adding entirely new features or significantly altering the bundle size.
All the vulnerabilities related to the version 4.3.28 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.