Compromised child renderer processes could obtain IPC access without nodeIntegrationInSubFrames being enabled
Package
Affected versions
< 15.5.5
>= 16.0.0, < 16.2.6
>= 17.0.0, < 17.2.0
>= 18.0.0-beta.1, <= 18.0.0-beta.5
Patched versions
15.5.5
16.2.6
17.2.0
18.0.0-beta.6
Description
Published by the National Vulnerability Database
Jun 13, 2022
Published to the GitHub Advisory Database
Jun 16, 2022
Reviewed
Jun 16, 2022
Last updated
Jan 27, 2023
Impact
This vulnerability allows a renderer with JS execution to obtain access to a new renderer process with
nodeIntegrationInSubFrames
enabled which in turn allows effective access toipcRenderer
.Please note the misleadingly named
nodeIntegrationInSubFrames
option does not implicitly grant Node.js access rather it depends on the existingsandbox
setting. If your application is sandboxed thennodeIntegrationInSubFrames
just gives access to the sandboxed renderer APIs (which includesipcRenderer
).If your application then additionally exposes IPC messages without IPC
senderFrame
validation that perform privileged actions or return confidential data this access toipcRenderer
can in turn compromise your application / user even with the sandbox enabled.Patches
This has been patched and the following Electron versions contain the fix:
18.0.0-beta.6
17.2.0
16.2.6
15.5.5
Workarounds
Ensure that all IPC message handlers appropriately validate
senderFrame
as per our security tutorial here.For more information
If you have any questions or comments about this advisory, email us at [email protected].
References