Esbuild 0.14.12 represents a minor version update over 0.14.11, primarily focused on incorporating the latest builds of its platform-specific dependencies. Both versions, however, share the same core functionality as an extremely fast JavaScript and CSS bundler and minifier, appealing to developers who prioritize build speed and efficiency. The description and license remain consistent across both releases, reinforcing the stability and ongoing support for the library.
The crucial distinction lies within the dependencies and optionalDependencies sections. Both versions list the same set of platform-specific packages like esbuild-linux-64, esbuild-darwin-64, and esbuild-windows-64 for various architectures. The only difference is that version 0.14.12 uses the 0.14.12 version of each of these platform-specific packages, while version 0.14.11 uses the 0.14.11 version. These packages are essential as they provide the pre-built binaries necessary for esbuild to run seamlessly across diverse operating systems without requiring compilation from source.
Developers should consider upgrading to 0.14.12 to leverage the potentially improved stability and bug fixes included in the updated platform-specific builds. While the core API and usage patterns are likely unchanged, keeping dependencies up-to-date is generally recommended for optimal performance and security. Furthermore, the releaseDate indicates a recent update, implying continued maintenance and community engagement, further solidifying esbuild as a reliable choice for modern web development workflows.
All the vulnerabilities related to the version 0.14.12 of the package
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.