Electron: Parent process code-sign check is spoofable
- 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.8, 40.9.0, 41.2.1, 42.0.0-beta.3, 40.9.1
- 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: total
Summary
Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. Prior to 39.8.8, 40.9.0, 41.2.1, and 42.0.0-beta.3, the check Electron uses on macOS to confirm it was launched by a same-signed parent process could be bypassed by a local process. Apps that enable fuse-based hardening restricting ELECTRON_RUN_AS_NODE and NODE_OPTIONS to same-signed parents rely on this check, and a local attacker could bypass it and run code inside the signed app, inheriting its TCC permissions and keychain access. This issue is fixed in 39.8.8, 40.9.0, 41.2.1, and 42.0.0-beta.3.
Timeline
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- CVE published
- Record last updated
Affected versions
- electron electron
fixed in 39.8.8; 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.8
- electronnpm
From 40.0.0-alpha.1 · fixed in 40.9.1
- 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