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.
The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Electron | Electronjs | * | 15.5.5 (excluding) |
| Electron | Electronjs | 16.0.1 (including) | 16.2.6 (excluding) |
| Electron | Electronjs | 17.0.1 (including) | 17.2.0 (excluding) |
| Electron | Electronjs | 16.0.0-beta1 (including) | 16.0.0-beta1 (including) |
| Electron | Electronjs | 16.0.0-beta2 (including) | 16.0.0-beta2 (including) |
| Electron | Electronjs | 16.0.0-beta3 (including) | 16.0.0-beta3 (including) |
| Electron | Electronjs | 16.0.0-beta4 (including) | 16.0.0-beta4 (including) |
| Electron | Electronjs | 16.0.0-beta5 (including) | 16.0.0-beta5 (including) |
| Electron | Electronjs | 16.0.0-beta6 (including) | 16.0.0-beta6 (including) |
| Electron | Electronjs | 16.0.0-beta7 (including) | 16.0.0-beta7 (including) |
| Electron | Electronjs | 16.0.0-beta8 (including) | 16.0.0-beta8 (including) |
| Electron | Electronjs | 16.0.0-beta9 (including) | 16.0.0-beta9 (including) |
| Electron | Electronjs | 17.0.0-beta1 (including) | 17.0.0-beta1 (including) |
| Electron | Electronjs | 17.0.0-beta2 (including) | 17.0.0-beta2 (including) |
| Electron | Electronjs | 17.0.0-beta3 (including) | 17.0.0-beta3 (including) |
| Electron | Electronjs | 17.0.0-beta4 (including) | 17.0.0-beta4 (including) |
| Electron | Electronjs | 17.0.0-beta5 (including) | 17.0.0-beta5 (including) |
| Electron | Electronjs | 17.0.0-beta6 (including) | 17.0.0-beta6 (including) |
| Electron | Electronjs | 17.0.0-beta7 (including) | 17.0.0-beta7 (including) |
| Electron | Electronjs | 17.0.0-beta8 (including) | 17.0.0-beta8 (including) |
| Electron | Electronjs | 17.0.0-beta9 (including) | 17.0.0-beta9 (including) |
| Electron | Electronjs | 18.0.0-beta1 (including) | 18.0.0-beta1 (including) |
| Electron | Electronjs | 18.0.0-beta2 (including) | 18.0.0-beta2 (including) |
| Electron | Electronjs | 18.0.0-beta3 (including) | 18.0.0-beta3 (including) |
| Electron | Electronjs | 18.0.0-beta4 (including) | 18.0.0-beta4 (including) |
| Electron | Electronjs | 18.0.0-beta5 (including) | 18.0.0-beta5 (including) |
Resources such as files and directories may be inadvertently exposed through mechanisms such as insecure permissions, or when a program accidentally operates on the wrong object. For example, a program may intend that private files can only be provided to a specific user. This effectively defines a control sphere that is intended to prevent attackers from accessing these private files. If the file permissions are insecure, then parties other than the user will be able to access those files. A separate control sphere might effectively require that the user can only access the private files, but not any other files on the system. If the program does not ensure that the user is only requesting private files, then the user might be able to access other files on the system. In either case, the end result is that a resource has been exposed to the wrong party.