Electron permission bypass in external protocol URL handling
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 versions 42.11.3, 43.7.0, 44.3.0, and 45.0.0-alpha.5, requests to open external protocol URLs could be attributed to a document other than the one that initiated them, causing the requestingUrl passed to session.setPermissionRequestHandler to identify trusted content for a launch requested by untrusted content. An application that grants openExternal based on the requesting origin and allows untrusted content to open or navigate windows could therefore allow that content to launch an OS-registered external application. This issue is fixed in versions 42.11.3, 43.7.0, 44.3.0, and 45.0.0-alpha.5.
From the CVE record · GitHub_M
Electron could attribute an external protocol request to a document other than the one that initiated it, causing session.setPermissionRequestHandler to see a trusted requesting URL for untrusted content. In applications that grant openExternal based on the requesting origin and let untrusted content open or navigate windows, that content could launch an OS-registered external application.
Check applications using npm electron versions below 42.11.3, 43.0.0-alpha.1 through versions below 43.7.0, 44.0.0-alpha.1 through versions below 44.3.0, or 45.0.0-alpha.1 through versions below 45.0.0-alpha.5.