Electron: Incorrect origin passed to permission request handler for iframe requests
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 38.8.6, 39.8.1, 40.8.1, and 41.0.0, when an iframe requests fullscreen, pointerLock, keyboardLock, openExternal, or media permissions, the origin passed to session.setPermissionRequestHandler() was the top-level page's origin rather than the requesting iframe's origin. Apps that grant permissions based on the origin parameter or webContents.getURL() may inadvertently grant permissions to embedded third-party content. The correct requesting URL remains available via details.requestingUrl. Apps that already check details.requestingUrl are not affected. This issue has been patched in versions 38.8.6, 39.8.1, 40.8.1, and 41.0.0.
From the CVE record · GitHub_M
Electron passed the top-level page's origin, rather than the requesting iframe's origin, to session.setPermissionRequestHandler() for certain iframe permission requests. An embedded third-party iframe could receive permissions inadvertently if the app grants them based on the origin parameter or webContents.getURL(). Apps that check details.requestingUrl are not affected.
Teams running npm electron versions below 38.8.6, 39.0.0-alpha.1 through 39.8.0, 40.0.0-alpha.1 through 40.8.0, or 41.0.0-alpha.1 through pre-41.0.0 should check their permission handlers.