Electron pointer lock permission bypass in cross-origin iframes
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.9, 43.7.6, 44.5.0, and 45.0.0-alpha.13, pointerLock permission requests from some cross-origin iframes caused session.setPermissionRequestHandler() to receive the top-level frame's requestingUrl and isMainFrame values instead of those of the requesting frame. An application that embeds untrusted iframe content and grants pointer lock based on the requesting origin could therefore grant the permission under the top-level page's identity. Applications that deny pointerLock for untrusted embedded content are not affected. This issue is fixed in versions 42.11.9, 43.7.6, 44.5.0, and 45.0.0-alpha.13.
From the CVE record · GitHub_M
In affected Electron versions, pointerLock requests from some cross-origin iframes can pass the top-level frame’s URL and main-frame status to session.setPermissionRequestHandler(). An application that embeds untrusted iframe content and grants pointer lock based on the requesting origin could grant permission under the top-level page’s identity; applications that deny pointerLock for untrusted embedded content are not affected.
Teams running Electron applications with npm electron versions below 42.11.9, from 43.0.0-alpha.1 to before 43.7.6, from 44.0.0-alpha.1 to before 44.5.0, or from 45.0.0-alpha.1 to before 45.0.0-alpha.13 should check.