Electron out-of-bounds read in frame subscription capture
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 42.11.6, 43.7.3, 44.4.3, and 45.0.0-alpha.9, frame data received from the GPU process for webContents.beginFrameSubscription was not fully validated by the main process. An attacker who had separately gained code execution in the GPU process could supply inconsistent frame geometry and cause the main process to read out-of-bounds memory while producing captured frame images, disclosing memory or crashing the application. This issue is fixed in versions 42.11.6, 43.7.3, 44.4.3, and 45.0.0-alpha.9.
From the CVE record · GitHub_M
Electron's main process did not fully validate GPU frame data used by webContents.beginFrameSubscription. An attacker who had separately gained code execution in the GPU process could supply inconsistent frame geometry, causing an out-of-bounds read that discloses memory or crashes the application while captured frame images are produced.
Teams running npm electron versions <42.11.6, >=43.0.0-alpha.1 <43.7.3, >=44.0.0-alpha.1 <44.4.3, or >=45.0.0-alpha.1 <45.0.0-alpha.9 should check their applications.