Electron: Pointer lock permission requests can be attributed to the wrong frame
- 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 42.11.9, 43.7.6, 44.5.0, 45.0.0-alpha.13
- 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: partial
Summary
Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. Prior to versions 42.11.9, 43.7.6, 44.5.0, and 45.0.0-alpha.13, pointerLock permission requests from some cross-origin iframes caused session.setPermissionRequestHandler() to receive the top-level frame's requestingUrl and isMainFrame values instead of those of the requesting frame. An application that embeds untrusted iframe content and grants pointer lock based on the requesting origin could therefore grant the permission under the top-level page's identity. Applications that deny pointerLock for untrusted embedded content are not affected. This issue is fixed in versions 42.11.9, 43.7.6, 44.5.0, and 45.0.0-alpha.13.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- electron electron
fixed in 42.11.9; From 43.0.0-alpha.1 · fixed in 43.7.6; From 44.0.0-alpha.1 · fixed in 44.5.0; From 45.0.0-alpha.1 · fixed in 45.0.0-alpha.13
- electronnpm
From 45.0.0-alpha.1 · fixed in 45.0.0-alpha.13
- electronnpm
From 44.0.0-alpha.1 · fixed in 44.5.0
- electronnpm
From 43.0.0-alpha.1 · fixed in 43.7.6
- electronnpm
fixed in 42.11.9