Exposure of Resource to Wrong Sphere in Electron
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 (JS), HTML, and CSS. A vulnerability in versions prior to 18.0.0-beta.6, 17.2.0, 16.2.6, and 15.5.5 allows a renderer with JS execution to obtain access to a new renderer process with `nodeIntegrationInSubFrames` enabled which in turn allows effective access to `ipcRenderer`. The `nodeIntegrationInSubFrames` option does not implicitly grant Node.js access. Rather, it depends on the existing sandbox setting. If an application is sandboxed, then `nodeIntegrationInSubFrames` just gives access to the sandboxed renderer APIs, which include `ipcRenderer`. If the application then additionally exposes IPC messages without IPC `senderFrame` validation that perform privileged actions or return confidential data this access to `ipcRenderer` can in turn compromise your application / user even with the sandbox enabled. Electron versions 18.0.0-beta.6, 17.2.0, 16.2.6, and 15.5.5 contain a fix for this issue. As a workaround, ensure that all IPC message handlers appropriately validate `senderFrame`.
From the CVE record · GitHub_M
In affected Electron versions, a renderer with JavaScript execution can access a new renderer process with `nodeIntegrationInSubFrames` enabled, gaining effective access to `ipcRenderer`. Even in a sandboxed application, this can compromise the application or user if IPC handlers perform privileged actions or return confidential data without validating `senderFrame`.
Teams using the npm `electron` package should check versions below 15.5.5, 16.0.0 through 16.2.5, 17.0.0 through 17.1.x, and 18.0.0-beta.1 through beta.5.