Electron: nodeIntegrationInWorker not correctly scoped in shared renderer processes
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.4, 40.8.4, and 41.0.0, the nodeIntegrationInWorker webPreference was not correctly scoped in all configurations. In certain process-sharing scenarios, workers spawned in frames configured with nodeIntegrationInWorker: false could still receive Node.js integration. Apps are only affected if they enable nodeIntegrationInWorker. Apps that do not use nodeIntegrationInWorker are not affected. This issue has been patched in versions 38.8.6, 39.8.4, 40.8.4, and 41.0.0.
From the CVE record · GitHub_M
In certain process-sharing configurations, workers spawned by frames with nodeIntegrationInWorker set to false can still receive Node.js integration. This affects only apps that enable nodeIntegrationInWorker; the input does not specify an attacker access path or user-interaction requirement.
Teams running npm electron versions below 38.8.6, 39.0.0-alpha.1 through below 39.8.4, 40.0.0-alpha.1 through below 40.8.4, or 41.0.0-alpha.1 through below 41.0.0 should check their apps.