Packages / electron / Security

HighVulnerabilityGHSA-w222-53c6-c86pCVE-2018-1000006Published 23 Jan 2018

Remote Code Execution in electron

Affected releases · electron

  • 1.x1.6.0 – 1.8.1Fixed in 1.8.2

On 1.x, the newest line:

npm install electron@1.8.2
45.x

  1. Not affected

    45.0.0

    1 release, latest

1.x

  1. Not affected

    1.3.1 – 1.5.1

    34 releases

  2. Affected

    1.6.0 – 1.6.15

    16 releases

  3. Fixed

    1.6.16 – 1.6.18

    3 releases

  4. Affected

    1.7.0 – 1.7.10

    11 releases

  5. Fixed

    1.7.11 – 1.7.16

    6 releases

  6. Affected

    1.8.0 – 1.8.1

    2 releases

  7. Fixed

    1.8.2 – 1.8.8

    7 releases

1131 stable releases of electron, oldest to newest, one row per major.

Is your project affected?

Paste your package.json, or type the range you declare for electron. It is read in your browser and sent nowhere.

What happens

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',
  '--'
])