Electron: Unquoted executable path in app.setLoginItemSettings on Windows
- 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 38.8.6, 39.8.1, 40.8.0, 41.0.0-beta.8
- 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: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- electron electron
fixed in 38.8.6; From 39.0.0-alpha.1 · fixed in 39.8.1; From 40.0.0-alpha.1 · fixed in 40.8.0; From 41.0.0-alpha.1 · fixed in 41.0.0-beta.8
- electronnpm
fixed in 38.8.6
- electronnpm
From 39.0.0-alpha.1 · fixed in 39.8.1
- electronnpm
From 40.0.0-alpha.1 · fixed in 40.8.0
- electronnpm
From 41.0.0-alpha.1 · fixed in 41.0.0-beta.8