Electron: Use-after-free in WebContents fullscreen, pointer-lock, and keyboard-lock permission callbacks
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.0, 40.7.0, and 41.0.0-beta.8, apps that register an asynchronous session.setPermissionRequestHandler() may be vulnerable to a use-after-free when handling fullscreen, pointer-lock, or keyboard-lock permission requests. If the requesting frame navigates or the window closes while the permission handler is pending, invoking the stored callback dereferences freed memory, which may lead to a crash or memory corruption. Apps that do not set a permission request handler, or whose handler responds synchronously, are not affected. This issue has been patched in versions 38.8.6, 39.8.0, 40.7.0, and 41.0.0-beta.8.
From the CVE record · GitHub_M
Electron apps with an asynchronous session.setPermissionRequestHandler() are vulnerable to a use-after-free during fullscreen, pointer-lock, or keyboard-lock permission requests. If the requesting frame navigates or the window closes while the handler is pending, invoking its stored callback may cause a crash or memory corruption. Apps without a permission request handler, or with one that responds synchronously, are not affected.
Teams using the npm electron package should check versions below 38.8.6, 39.0.0-alpha.1 through versions below 39.8.0, 40.0.0-alpha.1 through versions below 40.7.0, and 41.0.0-alpha.1 through versions below 41.0.0-beta.8.