Electron: Out-of-bounds read in second-instance IPC on macOS and Linux
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.1, 40.8.1, and 41.0.0, on macOS and Linux, apps that call app.requestSingleInstanceLock() were vulnerable to an out-of-bounds heap read when parsing a crafted second-instance message. Leaked memory could be delivered to the app's second-instance event handler. This issue is limited to processes running as the same user as the Electron app. Apps that do not call app.requestSingleInstanceLock() are not affected. Windows is not affected by this issue. This issue has been patched in versions 38.8.6, 39.8.1, 40.8.1, and 41.0.0.
From the CVE record · GitHub_M
On macOS and Linux, Electron apps that call app.requestSingleInstanceLock() can read beyond heap bounds when parsing a crafted second-instance message. A process running as the same user as the app could cause memory to be delivered to the app's second-instance event handler. Apps that do not call this API and Windows apps are not affected.
Engineers running npm electron versions below 38.8.6, 39.0.0-alpha.1 through versions below 39.8.1, 40.0.0-alpha.1 through versions below 40.8.1, or 41.0.0-alpha.1 through versions below 41.0.0 on macOS or Linux should check whether their app calls app.requestSingleInstanceLock().