Electron: Custom protocol with supportFetchAPI but not corsEnabled allows cross-origin reads
electron
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| electron npm |
|
|
electron
| Product | Affected | Fixed in |
|---|---|---|
| electron npm |
|
|
Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. Prior to 39.8.10, 40.9.3, 41.4.0, and 42.0.0, a custom scheme registered with supportFetchAPI: true but without corsEnabled: true was not subject to CORS enforcement. A page loaded from a remote origin could therefore fetch() or XMLHttpRequest that scheme cross-origin and read the full response body, rather than the read being blocked. Apps that serve sensitive data from such a scheme and load remote or untrusted content in a renderer are affected. This issue is fixed in versions 39.8.10, 40.9.3, 41.4.0, and 42.0.0.
From the CVE record · GitHub_M
Electron custom schemes registered with supportFetchAPI: true but without corsEnabled: true did not enforce CORS. In apps that serve sensitive data from such a scheme and load remote or untrusted content in a renderer, that content can make cross-origin fetch or XMLHttpRequest calls and read the full response body.
Check apps using npm electron versions earlier than 39.8.10, or affected 40.x, 41.x, or 42.0.0 prerelease versions.