Electron: Sandboxed preload code cache can be poisoned by a compromised renderer
- 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 42.10.0, 43.5.0, 44.0.0-beta.6
- 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. From 42.3.3 until 42.10.0, 43.5.0, and 44.0.0-beta.6, Electron's sandboxed preload code cache did not verify that a cached entry matched the preload it was served for. A compromised renderer could write attacker-controlled cache data and cause Electron to reuse it for a later load, executing the renderer's code in the more privileged preload context. The issue affects applications that load untrusted content. This issue is fixed in versions 42.10.0, 43.5.0, and 44.0.0-beta.6.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- electron electron
From 42.3.3 · fixed in 42.10.0; From 43.0.0-beta.1 · fixed in 43.5.0; From 44.0.0-alpha.1 · fixed in 44.0.0-beta.6
- electronnpm
From 42.3.3 · fixed in 42.10.0
- electronnpm
From 43.0.0-beta.1 · fixed in 43.5.0
- electronnpm
From 44.0.0-alpha.1 · fixed in 44.0.0-beta.6