CVEvulnerability

CVE-2022-29247

9.8 CRITICAL Published 2022-06-13 Modified 2026-06-17 Official page ↗
Status
Modified
Published
2022-06-13
Last modified
2026-06-17
Assigner
[email protected]
CVSS 3.1 ([email protected])
2.2 LOW — CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:N/A:N
CVSS 3.1 ([email protected])
9.8 CRITICAL — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS 2.0 ([email protected])
6.8 MEDIUM — AV:N/AC:M/Au:N/C:P/I:P/A:P
Weaknesses
CWE-668

Description

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`.

Affected configurations

• electronjs electron (< 15.5.5) • electronjs electron (>= 16.0.1 < 16.2.6) • electronjs electron (>= 17.0.1 < 17.2.0) • electronjs electron 16.0.0 • electronjs electron 17.0.0 • electronjs electron 18.0.0

Related

Weakness · CWE (1)

  • CWE-668 Exposure of Resource to Wrong Sphere weakness

References