Electron: Sandboxed iframes can launch external protocol handlers
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.8, 40.9.0, 41.2.1, and 42.0.0-beta.3, requests to open external protocol URLs from web content did not take iframe sandbox restrictions into account, so a sandboxed iframe could cause an OS-registered external application to be launched. The frame sandbox state was also not made available to the app permission handlers, affecting apps that render untrusted content in sandboxed iframes and grant the openExternal permission by default when no setPermissionRequestHandler is installed. This issue is fixed in 39.8.8, 40.9.0, 41.2.1, and 42.0.0-beta.3.
From the CVE record · GitHub_M
Electron did not account for iframe sandbox restrictions when web content requested an external protocol URL. In apps that render untrusted content in sandboxed iframes and grant openExternal permission by default without a setPermissionRequestHandler, a sandboxed iframe could launch an OS-registered external application.
Check apps using the npm electron package in versions <39.8.8, >=40.0.0-alpha.1 <40.9.0, >=41.0.0-alpha.1 <41.2.1, or >=42.0.0-alpha.1 <42.0.0-beta.3.