Electron: window.open features string controls some window options considered privileged
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, some window options supplied by web content in the window.open() features string were applied to the new BrowserWindow without an allowlist. Untrusted content could set window options it should not control, including options that cause the main process to access attacker-chosen file or network paths, when untrusted content can call window.open() and the app does not override child window options via setWindowOpenHandler or overrideBrowserWindowOptions. 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 applied some window options from web content’s window.open() features string to a new BrowserWindow without an allowlist. If untrusted content can call window.open() and the app does not override child window options, that content can set options that cause the main process to access attacker-chosen file or network paths.
Teams using the npm electron package should check versions below 39.8.8, 40.0.0-alpha.1 through versions below 40.9.0, 41.0.0-alpha.1 through versions below 41.2.1, and 42.0.0-alpha.1 through versions below 42.0.0-beta.3.