Electron: Out-of-bounds read in second-instance IPC on macOS and Linux
- 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.1, 40.8.1, 41.0.0
- 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 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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- electron electron
fixed in 38.8.6; From 39.0.0-alpha.1 · fixed in 39.8.1; From 40.0.0-alpha.1 · fixed in 40.8.1; From 41.0.0-alpha.1 · fixed in 41.0.0
- electronnpm
fixed in 38.8.6
- electronnpm
From 39.0.0-alpha.1 · fixed in 39.8.1
- electronnpm
From 40.0.0-alpha.1 · fixed in 40.8.1
- electronnpm
From 41.0.0-alpha.1 · fixed in 41.0.0