Electron: Unquoted executable path in app.setLoginItemSettings 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.0, and 41.0.0-beta.8, on Windows, app.setLoginItemSettings({openAtLogin: true}) wrote the executable path to the Run registry key without quoting. If the app is installed to a path containing spaces, an attacker with write access to an ancestor directory may be able to cause a different executable to run at login instead of the intended app. On a default Windows install, standard system directories are protected against writes by standard users, so exploitation typically requires a non-standard install location. This issue has been patched in versions 38.8.6, 39.8.1, 40.8.0, and 41.0.0-beta.8.
From the CVE record · GitHub_M
On Windows, Electron writes an unquoted executable path to the Run registry key when an app enables open-at-login. If the app is installed in a path containing spaces, a local attacker with write access to an ancestor directory may cause a different executable to run at login. This typically requires a non-standard install location because standard system directories are protected from writes by standard users.
Check Windows apps using npm electron versions <38.8.6, >=39.0.0-alpha.1 <39.8.1, >=40.0.0-alpha.1 <40.8.0, or >=41.0.0-alpha.1 <41.0.0-beta.8.