HighGHSA-w222-53c6-c86pCVE-2018-1000006

Remote Code Execution in electron

Published 23 Jan 2018 · Updated 8 Nov 2023

Affected packages

Affected
>=1.7.0 <1.7.11
Fixed in
1.7.11
Update to the fixed version for your release line, for example:npm install electron@1.7.11
Affected
>=1.6.0 <1.6.16
Fixed in
1.6.16
Update to the fixed version for your release line, for example:npm install electron@1.6.16
Affected
>=1.8.0 <1.8.2-beta.4
Fixed in
1.8.2-beta.4
Update to the fixed version for your release line, for example:npm install electron@1.8.2-beta.4

Details

Affected versions of electron may be susceptible to a remote code execution flaw when certain conditions are met: 1. The electron application is running on Windows. 2. The electron application registers as the default handler for a protocol, such as nodeapp://.

This vulnerability is caused by a failure to sanitize additional arguments to chromium in the command line handler for Electron.

MacOS and Linux are not vulnerable.

Recommendation

Update electron to a version that is not vulnerable. If updating is not possible, the electron team has provided the following guidance:

If for some reason you are unable to upgrade your Electron version, you can append -- as the last argument when calling app.setAsDefaultProtocolClient, which prevents Chromium from parsing further options. The double dash -- signifies the end of command options, after which only positional parameters are accepted.

app.setAsDefaultProtocolClient(protocol, process.execPath, [
  '--your-switches-here',
  '--'
])

Is GHSA-w222-53c6-c86p in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected electron, and gives you the command that fixes it.

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.