@umijs/bundler-esbuild is a powerful bundler tailored for UmiJS projects, streamlining the build process with the speed and efficiency of esbuild. Version 4.3.16 and 4.3.15 showcase subtle but important differences, primarily revolving around dependency updates and internal improvements. Both versions share a core set of dependencies crucial for modern web development, including postcss for CSS transformations, @umijs/utils and @umijs/bundler-utils for internal utilities within the UmiJS ecosystem, enhanced-resolve for smart module resolution, postcss-preset-env for leveraging future CSS features, and postcss-flexbugs-fixes for ensuring cross-browser compatibility with flexbox layouts. Developers using either version can expect robust CSS processing and reliable module handling. The devDependencies in both versions include @alitajs/postcss-plugin-px2rem, suggesting support for converting pixel units to rem units for responsive design.
The key difference lies in the @umijs/utils and @umijs/bundler-utils dependencies. Version 4.3.16 utilizes @umijs/utils and @umijs/bundler-utils at version "4.3.16" while version 4.3.15 uses the previous "4.3.15", indicating internal updates and bug fixes within the UmiJS core libraries. For developers, upgrading from 4.3.15 to 4.3.16 likely brings improved stability, performance enhancements, and potentially new features or bug fixes inherited from the updated UmiJS utilities. The release date also indicates a more recent update for 4.3.16. While the file count and unpacked size remain the same, the newer version represents the most up-to-date and recommended choice for developers seeking the latest improvements and fixes.
All the vulnerabilities related to the version 4.3.16 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 i
npm run watch
fetch('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.