Electron: Off-screen rendering trusts GPU-supplied geometry over shared-memory size
- 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 39.8.10, 40.9.0, 41.2.1, 42.0.0-beta.3
- 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 39.8.10, 40.9.0, 41.2.1, and 42.0.0-beta.3, offscreen rendering frame data received from the GPU process was not fully validated by the main process. A compromised GPU process could cause the main process to read out-of-bounds memory while producing paint event images, disclosing memory or crashing the app. This issue is fixed in 39.8.10, 40.9.0, 41.2.1, and 42.0.0-beta.3.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- electron electron
fixed in 39.8.10; From 40.0.0-alpha.1 · fixed in 40.9.0; From 41.0.0-alpha.1 · fixed in 41.2.1; From 42.0.0-alpha.1 · fixed in 42.0.0-beta.3
- electronnpm
fixed in 39.8.10
- electronnpm
From 40.0.0-alpha.1 · fixed in 40.9.0
- electronnpm
From 41.0.0-alpha.1 · fixed in 41.2.1
- electronnpm
From 42.0.0-alpha.1 · fixed in 42.0.0-beta.3