Esbuild, a renowned JavaScript and CSS bundler and minifier celebrated for its exceptional speed, has released version 0.17.15 following version 0.17.14. While the core functionality and overarching description remain consistent between the two versions, a closer inspection reveals nuanced differences relevant to developers.
The primary distinction lies in the version numbers of the package's myriad dependencies. Both stable versions rely on a suite of platform-specific packages prefixed with @esbuild/, covering a wide range of operating systems and architectures, including Linux (arm, x64, ia32, arm64, ppc64, s390x, loong64, riscv64, mips64el), Windows (x64, ia32, arm64), macOS (x64, arm64), Android (arm, x64, arm64), FreeBSD (x64, arm64), NetBSD (x64), SunOS (x64), and OpenBSD (x64). In version 0.17.15, these dependencies are all updated to version 0.17.15 to be consistent with the main package version. Similarly, version 0.17.14 relies on version 0.17.14 of the same dependencies. This indicates that the update likely incorporates bug fixes, performance improvements, or compatibility adjustments within these platform-specific components.
Developers considering upgrading should note the releaseDate. Version 0.17.15 was released on April 1, 2023, whereas version 0.17.14 was released on March 26, 2023. This time difference suggests that 0.17.15 contains potentially important updates addressed after the release of 0.17.14. Furthermore, the consistency of fileCount and unpackedSize between the two versions implies no significant changes in the overall size or number of files within the package. Thus, the upgrade should be relatively seamless, primarily involving updating the dependency versions. Esbuild remains a compelling choice for developers seeking a fast and efficient build tool, and staying up-to-date with the latest minor version ensures access to the latest enhancements and bug fixes.
All the vulnerabilities related to the version 0.17.15 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.