Electron: Use-after-free in WebContents fullscreen, pointer-lock, and keyboard-lock permission callbacks
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 38.8.6, 39.8.0, 40.7.0, 41.0.0-beta.8
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- electron electron
fixed in 38.8.6; From 39.0.0-alpha.1 · fixed in 39.8.0; From 40.0.0-alpha.1 · fixed in 40.7.0; From 41.0.0-alpha.1 · fixed in 41.0.0-beta.8
- electronnpm
fixed in 38.8.6
- electronnpm
From 39.0.0-alpha.1 · fixed in 39.8.0
- electronnpm
From 40.0.0-alpha.1 · fixed in 40.7.0
- electronnpm
From 41.0.0-alpha.1 · fixed in 41.0.0-beta.8