Electron: DevTools JavaScript Injection via Unsanitized Dock State Parameter
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.7, 40.9.0, 41.2.0, and 42.0.0-beta.1, the mode option of webContents.openDevTools() was not sanitized before use by the DevTools frontend. If an attacker can influence this value, script under their control may run in the DevTools context, which in unsandboxed configurations has access to Node.js, including when untrusted input reaches the mode argument of openDevTools() or untrusted content calls openDevTools() on a webview it embeds. This issue is fixed in 39.8.7, 40.9.0, 41.2.0, and 42.0.0-beta.1.
From the CVE record · GitHub_M
Electron did not sanitize the mode option of webContents.openDevTools() before passing it to the DevTools frontend. If an attacker can influence that option—through untrusted input or untrusted content calling openDevTools() on an embedded webview—their script may run in the DevTools context, with Node.js access in unsandboxed configurations. Network access, authentication, and user-interaction requirements are not specified.
Engineers using the npm electron package should check versions below 39.8.7, from 40.0.0-alpha.1 to below 40.9.0, from 41.0.0-alpha.1 to below 41.2.0, or from 42.0.0-alpha.1 to below 42.0.0-beta.1.