ghsa-q43m-ffwr-rpcc
Vulnerability from github
Published
2019-02-18 23:58
Modified
2021-01-08 18:18
Summary
SSL Validation Defaults to False in electron-packager
Details

Affected versions of electron-packager configure the generated application to disable SSL certificate verification by default.

This could allow an attacker with a privileged network position to launch a Man In The Middle (MITM) attack on the install process, intercepting the step where electron-packager downloads Electron for supported target platforms and architectures, and replacing the valid download with a tampered malicious one.

This only affects users using the electron-packager CLI. The strict-ssl option defaults to true for the node.js API.

Recommendation

  1. Update to version 7.0.0 or later.
  2. Delete the electron-download cache folder, which is by default located at ~/.electron.
Show details on source website

To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "npm",
        "name": "electron-packager"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "5.2.1"
            },
            {
              "fixed": "7.0.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2016-10534"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-295"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2020-06-16T21:50:47Z",
    "nvd_published_at": null,
    "severity": "LOW"
  },
  "details": "Affected versions of `electron-packager` configure the generated application to disable SSL certificate verification by default. \n\nThis could allow an attacker with a privileged network position to launch a Man In The Middle (MITM) attack on the install process, intercepting the step where electron-packager downloads Electron for supported target platforms and architectures, and replacing the valid download with a tampered malicious one.\n\nThis only affects users using the electron-packager CLI. The strict-ssl option defaults to true for the node.js API.\n\n\n## Recommendation\n\n1. Update to version 7.0.0 or later.\n2. Delete the `electron-download` cache folder, which is by default located at `~/.electron`.",
  "id": "GHSA-q43m-ffwr-rpcc",
  "modified": "2021-01-08T18:18:07Z",
  "published": "2019-02-18T23:58:24Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2016-10534"
    },
    {
      "type": "WEB",
      "url": "https://github.com/electron-userland/electron-packager/issues/333"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/advisories/GHSA-q43m-ffwr-rpcc"
    },
    {
      "type": "WEB",
      "url": "https://www.npmjs.com/advisories/104"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [],
  "summary": "SSL Validation Defaults to False in electron-packager"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.