Electron: Registry key path injection in app.setAsDefaultProtocolClient on Windows
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 Windows, app.setAsDefaultProtocolClient(protocol) did not validate the protocol name before writing to the registry. Apps that pass untrusted input as the protocol name may allow an attacker to write to arbitrary subkeys under HKCU\Software\Classes\, potentially hijacking existing protocol handlers. Apps are only affected if they call app.setAsDefaultProtocolClient() with a protocol name derived from external or untrusted input. Apps that use a hardcoded protocol name are not affected. 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 Windows, Electron did not validate protocol names passed to app.setAsDefaultProtocolClient() before writing to the registry. An attacker may be able to write to arbitrary subkeys under HKCU\Software\Classes\ and hijack existing protocol handlers if an app passes an externally supplied or untrusted protocol name; apps using a hardcoded name are not affected.
Teams running Windows apps built with npm electron versions <38.8.6, >=39.0.0-alpha.1 <39.8.1, >=40.0.0-alpha.1 <40.8.1, or >=41.0.0-alpha.1 <41.0.0 should check their usage of this API.