Electron's AutoUpdater module fails to validate certain nested components of the bundle
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 (JS), HTML, and CSS. A vulnerability in versions prior to 18.0.0-beta.6, 17.2.0, 16.2.6, and 15.5.5 allows attackers who have control over a given apps update server / update storage to serve maliciously crafted update packages that pass the code signing validation check but contain malicious code in some components. This kind of attack would require significant privileges in a potential victim's own auto updating infrastructure and the ease of that attack entirely depends on the potential victim's infrastructure security. Electron versions 18.0.0-beta.6, 17.2.0, 16.2.6, and 15.5.5 contain a fix for this issue. There are no known workarounds.
From the CVE record · GitHub_M
Electron’s update validation can accept a maliciously crafted package containing malicious code in some components. An attacker must control an app’s update server or update storage, which requires significant privileges in the app’s auto-update infrastructure.
Engineers running apps with npm electron versions below 15.5.0, 16.0.0–16.1.x, 17.0.0–17.1.x, or 18.0.0-beta.1 through beta.5 should check their deployments.