Esbuild version 0.10.2 represents a minor but notable iteration in the evolution of this blazingly fast JavaScript bundler and minifier. Released on March 27, 2021, just a day after version 0.10.1, it maintains the core functionality described as offering extremely high-performance bundling and minification. Both versions share identical file counts and unpacked sizes, suggesting focused and efficient updates rather than a complete overhaul. The MIT license continues to ensure broad usability and integration within various project types.
Developers adopting esbuild, even within these minor releases, benefit from its speed advantage, crucial for optimizing build times and improving the overall development workflow. While the provided data doesn't specify the exact nature of the changes between 0.10.1 and 0.10.2, the rapid release cycle implies potential bug fixes, performance enhancements, or resolution of compatibility issues discovered shortly after the earlier version. Users experiencing any anomalies with 0.10.1 might find upgrading to 0.10.2 immediately beneficial. The consistent repository URL points to the active development and maintenance by the esbuild team, signaling a commitment to stability and ongoing improvements for developers relying on this tool for their JavaScript bundling needs. Always consult the official changelog on the GitHub repository for detailed release notes.
All the vulnerabilities related to the version 0.10.2 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 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.