Vulnerabilities

146 via 153 paths

Dependencies

187

Source

npm

Find, fix and prevent vulnerabilities in your code.

Severity
  • 8
  • 99
  • 35
  • 4
Status
  • 146
  • 0
  • 0

critical severity

Arbitrary Code Execution

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@1.6.14.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Arbitrary Code Execution. An arbitrary code execution vulnerability was discovered in Google Chromium, affecting many versions of Electron. Any Electron app that accesses remote content is vulnerable to this exploit, regardless of whether the sandbox option is enabled.

Remediation

Upgrade electron to version 1.6.14, 1.7.8, 1.8.1 or higher.

References

critical severity

Arbitrary Code Injection

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@1.4.15.

Overview

electron is a framework for creating native applications with web technologies like JavaScript, HTML, and CSS. It takes care of the hard parts so you can focus on the core of your application.

Affected versions of the package are vulnerable to Arbitrary Code Injection. A malicious user can create a specially crafted site which will be loaded in the preload script and would run in the main JavaScript context.

Remediation

Upgrade electron to version 1.4.15 or higher.

References

critical severity

Out-of-bounds

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@10.4.4.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Out-of-bounds via the V8 component in Chrome.

Remediation

Upgrade electron to version 11.4.4, 10.4.4, 12.0.6 or higher.

References

critical severity

Out-of-bounds Write

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@11.4.10.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Out-of-bounds Write via ANGLE in Chrome.

Remediation

Upgrade electron to version 12.0.13, 11.4.10 or higher.

References

critical severity

Type Confusion

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@12.2.3.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Type Confusion via the V8 module in Chromium.

Remediation

Upgrade electron to version 14.2.1, 13.6.2, 12.2.3 or higher.

References

critical severity

Use After Free

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@9.4.1.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Use After Free. An unknown vunerability exists in Chrome.

Remediation

Upgrade electron to version 9.4.1, 10.3.2 or higher.

References

critical severity

Use After Free

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@11.2.2.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Use After Free via handling of cookies.

Remediation

Upgrade electron to version 9.4.2, 10.3.1, 11.2.2 or higher.

References

critical severity

Directory Traversal

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@1.6.16.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Directory Traversal. Electron apps running on Windows that register themselves as the default handler for a protocol, like myapp://, are vulnerable.

Such apps can be affected regardless of how the protocol is registered, e.g. using native code, the Windows registry, or Electron's app.setAsDefaultProtocolClient API.

Note: MacOS and Linux are not affected by this vulnerability.

Details

A Directory Traversal attack (also known as path traversal) aims to access files and directories that are stored outside the intended folder. By manipulating files with "dot-dot-slash (../)" sequences and its variations, or by using absolute file paths, it may be possible to access arbitrary files and directories stored on file system, including application source code, configuration, and other critical system files.

Directory Traversal vulnerabilities can be generally divided into two types:

  • Information Disclosure: Allows the attacker to gain information about the folder structure or read the contents of sensitive files on the system.

st is a module for serving static files on web pages, and contains a vulnerability of this type. In our example, we will serve files from the public route.

If an attacker requests the following URL from our server, it will in turn leak the sensitive private key of the root user.

curl http://localhost:8080/public/%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/root/.ssh/id_rsa

Note %2e is the URL encoded version of . (dot).

  • Writing arbitrary files: Allows the attacker to create or replace existing files. This type of vulnerability is also known as Zip-Slip.

One way to achieve this is by using a malicious zip archive that holds path traversal filenames. When each filename in the zip archive gets concatenated to the target extraction folder, without validation, the final path ends up outside of the target folder. If an executable or a configuration file is overwritten with a file containing malicious code, the problem can turn into an arbitrary code execution issue quite easily.

The following is an example of a zip archive with one benign file and one malicious file. Extracting the malicious file will result in traversing out of the target folder, ending up in /root/.ssh/ overwriting the authorized_keys file:

2018-04-15 22:04:29 .....           19           19  good.txt
2018-04-15 22:04:42 .....           20           20  ../../../../../../root/.ssh/authorized_keys

Remediation

Upgrade electron to version 1.6.16, 1.7.11, 1.8.2-beta.4 or higher.

References

high severity

Access of Resource Using Incompatible Type ('Type Confusion')

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@11.4.9.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Access of Resource Using Incompatible Type ('Type Confusion'). Type confusion in V8 in Google Chrome allows a remote attacker to potentially exploit heap corruption via a crafted HTML page.

Remediation

Upgrade electron to version 12.0.12, 11.4.9 or higher.

References

high severity

Access Restriction Bypass

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@12.2.0.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Access Restriction Bypass in Blink.

Remediation

Upgrade electron to version 13.5.0, 12.2.0 or higher.

References

high severity

Heap Buffer Overflow

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@10.4.1.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Heap Buffer Overflow via WebAudio.

Remediation

Upgrade electron to version 11.4.0, 10.4.1 or higher.

References

high severity

Heap Overflow

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@6.1.10.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Heap Overflow. A Heap buffer overflow exists in the media component of Google Chrome, which also affects chromium.

Remediation

Upgrade electron to version 6.1.10, 7.2.2, 8.2.1 or higher.

References

high severity

Heap-based Buffer Overflow

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@9.4.0.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Heap-based Buffer Overflow. A heap buffer overflow flaw was found in the UI component of the Chromium browser.

Remediation

Upgrade electron to version 9.4.0, 10.2.0 or higher.

References

high severity

Heap-based Buffer Overflow

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@12.2.3.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Heap-based Buffer Overflow via the WebRTC module in Chromium.

Remediation

Upgrade electron to version 14.2.0, 13.5.2, 12.2.3 or higher.

References

high severity

Improper Access Control

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@9.4.0.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Improper Access Control. An insufficient policy enforcement flaw was found in the networking component of chromium.

Remediation

Upgrade electron to version 9.4.0, 10.1.7 or higher.

References

high severity

Improper Access Control

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@6.1.10.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Improper Access Control. It has an inappropriate implementation in V8.

Remediation

Upgrade electron to version 6.1.10, 7.2.2, 8.2.1 or higher.

References

high severity

Improper Input Validation

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@9.4.0.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Improper Input Validation. An insufficient data validation flaw was found in the WASM component of the Chromium browser.

Remediation

Upgrade electron to version 9.4.0, 10.1.7 or higher.

References

high severity

Integer Overflow

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@10.4.4.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Integer Overflow via Chromium in Mojo.

Remediation

Upgrade electron to version 10.4.4 or higher.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@10.4.4.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Integer Overflow or Wraparound via the Mojo component of chromium.

Remediation

Upgrade electron to version 10.4.4, 12.0.6 or higher.

References

high severity

Out-of-Bounds

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@10.4.1.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Out-of-Bounds. Object lifecycle issue in audio.

Remediation

Upgrade electron to version 11.4.0, 10.4.1 or higher.

References

high severity

Out-of-bounds Write

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@10.4.1.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Out-of-bounds Write via a data race in the audio component. A remote attacker could potentially exploit heap corruption using a crafted HTML page.

Remediation

Upgrade electron to version 10.4.1, 11.4.1 or higher.

References

high severity

Type Confusion

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@10.4.7.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Type Confusion in V8.

Remediation

Upgrade electron to version 12.0.10, 11.4.8, 10.4.7 or higher.

References

high severity

Type Confusion

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@11.4.11.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Type Confusion in V8 via Chrome.

Remediation

Upgrade electron to version 12.0.16, 11.4.11 or higher.

References

high severity

Type Confusion

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@12.2.0.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Type Confusion via Blink layout in Chrome.

Remediation

Upgrade electron to version 13.5.0, 12.2.0 or higher.

References

high severity

Type Confusion

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@12.2.0.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Type Confusion in Blink layout.

Remediation

Upgrade electron to version 13.5.0, 12.2.0 or higher.

References

high severity
new

Type Confusion

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@13.6.3.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Type Confusion in V8. This allows a remote attacker to potentially exploit heap corruption via a crafted HTML page.

Remediation

Upgrade electron to version 13.6.3, 14.2.2, 15.3.3 or higher.

References

high severity

Type Confusion

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@7.3.1.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Type Confusion in V8.

Remediation

Upgrade electron to version 7.3.1 or higher.

References

high severity

Use After Free

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@8.5.4.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Use After Free via the site isolation.

Remediation

Upgrade electron to version 8.5.4, 9.3.5, 10.1.6 or higher.

References

high severity

Use After Free

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@9.4.0.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Use After Free. A use after free flaw was found in the PPAPI component of the Chromium browser.

Remediation

Upgrade electron to version 9.4.0, 10.2.0 or higher.

References

high severity

Use After Free

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@9.4.4.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Use After Free in Media.

Remediation

Upgrade electron to version 11.2.1, 9.4.4 or higher.

References

high severity

Use After Free

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@9.4.4.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Use After Free. It hands sub-queries with both a correlated WHERE clause and a HAVING 0 clause where the parent query is itself an aggregate.

Remediation

Upgrade electron to version 11.2.1, 9.4.4 or higher.

References

high severity

Use After Free

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@10.4.1.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Use After Free. When a LayoutInline is removed, LineBoxList::DirtyLinesFromChangedChild tries to mark affected RootInlineBox dirty.

When the |LayoutInline| to be removed is culled, it tries to find the RootInlineBox from its previous siblings, then look for its previous and next RootInlineBoxes.

Occasionally, the next next line of the previous sibling is wrapped at the LayoutInline, and that its LineBreakObj() holds the reference to the LayoutInline. This patch marks such RootInlineBox dirty.

Remediation

Upgrade electron to version 11.4.0, 10.4.1 or higher.

References

high severity

Use After Free

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@10.4.1.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Use After Free in WebRTC.

Remediation

Upgrade electron to version 11.4.0, 10.4.1 or higher.

References

high severity

Use After Free

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@10.4.2.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Use After Free. It allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

Remediation

Upgrade electron to version 10.4.2, 11.4.1 or higher.

References

high severity

Use After Free

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@10.4.4.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Use After Free via a vulnerability that exists in Blink in Chromium. A remote attacker can trick the victim to visit a specially crafted web page, trigger a use-after-free error and execute arbitrary code on the system.

Remediation

Upgrade electron to version 11.4.4, 10.4.4 or higher.

References

high severity

Use After Free

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@10.4.4.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Use After Free via Chrome which allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

Remediation

Upgrade electron to version 12.0.5, 11.4.4, 10.4.4 or higher.

References

high severity

Use After Free

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@10.4.4.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Use After Free via chromium which allows a remote attacker to potentially exploit heap corruption via a crafted HTML page.

Remediation

Upgrade electron to version 12.0.5, 11.4.4, 10.4.4 or higher.

References

high severity

Use After Free

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@10.4.4.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Use After Free via Aura in Google Chrome which allowed a remote attacker who had compromised the renderer process to potentially exploit heap corruption via a crafted HTML page.

Remediation

Upgrade electron to version 12.0.5, 11.4.4, 10.4.4 or higher.

References

high severity

Use After Free

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@10.4.4.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Use After Free via the Navigation component of chromium.

Remediation

Upgrade electron to version 10.4.4, 11.4.4, 12.0.6 or higher.

References

high severity

Use After Free

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@10.4.4.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Use After Free in the chromium extensions resource.

Remediation

Upgrade electron to version 11.4.4, 10.4.4 or higher.

References

high severity

Use After Free

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@10.4.7.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Use After Free in File API.

Remediation

Upgrade electron to version 12.0.10, 11.4.8, 10.4.7 or higher.

References

high severity

Use After Free

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@10.4.7.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Use After Free in Notifications.

Remediation

Upgrade electron to version 12.0.10, 11.4.8, 10.4.7 or higher.

References

high severity

Use After Free

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@11.4.9.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Use After Free. Use after free in Loader in Google Chrome allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

Remediation

Upgrade electron to version 12.0.12, 11.4.9 or higher.

References

high severity

Use After Free

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@11.4.9.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Use After Free in BFCache in Google Chrome, which allows a remote attacker to potentially exploit heap corruption via a crafted HTML page.

Remediation

Upgrade electron to version 12.0.13, 11.4.9 or higher.

References

high severity

Use After Free

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@11.4.10.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Use After Free in WebGL.

Remediation

Upgrade electron to version 12.0.13, 11.4.10 or higher.

References

high severity

Use After Free

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@11.4.10.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Use After Free in WebRTC.

Remediation

Upgrade electron to version 12.0.14, 11.4.10 or higher.

References

high severity

Use After Free

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@11.4.10.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Use After Free in WebAudio.

Remediation

Upgrade electron to version 12.0.14, 11.4.10 or higher.

References

high severity

Use After Free

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@11.4.11.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Use After Free in Blink XSLT.

Remediation

Upgrade electron to version 12.0.16, 11.4.11 or higher.

References

high severity

Use After Free

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@11.4.11.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Use After Free in WebSerial via Chrome.

Remediation

Upgrade electron to version 12.0.16, 11.4.11 or higher.

References

high severity

Use After Free

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@11.4.11.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Use After Free in V8 via Chrome.

Remediation

Upgrade electron to version 12.0.16, 11.4.11 or higher.

References

high severity

Use After Free

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@11.4.11.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Use After Free in GPU.

Remediation

Upgrade electron to version 13.1.8, 12.0.16, 11.4.11 or higher.

References

high severity

Use After Free

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@11.4.11.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Use After Free in Autofill.

Remediation

Upgrade electron to version 12.0.16, 11.4.11 or higher.

References

high severity

Use After Free

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@12.2.0.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Use After Free in Indexed DB API.

Remediation

Upgrade electron to version 13.5.0, 12.2.0 or higher.

References

high severity

Use After Free

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@2.0.18.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Use After Free via the Chromium FileReader.

Note: This vulnerability affects all software based on Chromium, including Electron.

Remediation

Upgrade electron to version 2.0.18, 3.0.16, 3.1.6, 4.0.8 or higher.

References

high severity

Use After Free

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@12.2.2.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Use After Free via heap corruption through a crafted HTML page.

Remediation

Upgrade electron to version 14.1.1, 13.5.2, 12.2.2 or higher.

References

high severity

Use After Free

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@12.2.2.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Use After Free in the file system API, through a heap corruption via a crafted HTML page.

Remediation

Upgrade electron to version 14.1.1, 13.5.2, 12.2.2 or higher.

References

high severity

Use After Free

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@12.2.3.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Use After Free via the Garbage Collection module in Chromium.

Remediation

Upgrade electron to version 14.2.1, 13.6.2, 12.2.3 or higher.

References

high severity

Use After Free

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@13.6.2.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Use After Free via the Web Transport module in Chromium.

Remediation

Upgrade electron to version 14.2.1, 13.6.2 or higher.

References

high severity
new

Use After Free

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@13.6.3.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Use After Free in loader in Google Chrome. This allows a remote attacker to potentially exploit heap corruption via a crafted HTML page.

Remediation

Upgrade electron to version 13.6.3, 14.2.2, 15.3.3 or higher.

References

high severity
new

Use After Free

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@16.0.0.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Use After Free in the storage foundation, which allows a remote attacker to potentially exploit heap corruption via a crafted HTML page

Remediation

Upgrade electron to version 16.0.0 or higher.

References

high severity
new

Use After Free

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@13.6.6.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Use After Free via file API in Google Chrome prior to 96.0.4664.93. It allows a remote attacker who have compromised the renderer process to potentially exploit heap corruption via a crafted HTML page.

Remediation

Upgrade electron to version 13.6.6, 14.2.4, 15.3.5 or higher.

References

high severity

Use After Free

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@6.1.10.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Use After Free. Multiple user after free vulnerabilities exists in the WebAudio component of chromium.

Remediation

Upgrade electron to version 6.1.10, 7.2.2, 8.2.1 or higher.

References

high severity

Use After Free

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@6.1.10.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Use After Free. It allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

Remediation

Upgrade electron to version 6.1.10, 7.2.2, 8.2.1 or higher.

References

high severity

Use After Free

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@6.1.10.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Use After Free via the audio component. It allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

Remediation

Upgrade electron to version 6.1.10, 7.2.2, 8.2.1 or higher.

References

high severity

Use After Free

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@7.2.2.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Use After Free via the audio component.

Remediation

Upgrade electron to version 8.2.1, 7.2.2 or higher.

References

high severity

Use After Free

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@6.1.10.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Use After Free. It allows a remote attacker to potentially exploit heap corruption via a crafted HTML page.

Remediation

Upgrade electron to version 6.1.10, 7.2.2, 8.2.0 or higher.

References

high severity

Use After Free

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@8.3.1.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Use After Free in WebRTC.

Remediation

Upgrade electron to version 8.3.1 or higher.

References

high severity

Improper Input Validation

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@10.4.2.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Improper Input Validation. It allowed a remote attacker to leak cross-origin data via a crafted HTML page.

Remediation

Upgrade electron to version 10.4.2, 11.4.1 or higher.

References

high severity

Out-of-Bounds

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@10.4.2.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Out-of-Bounds. Out of bounds memory access in V8 in Google Chrome prior to 89.0.4389.72 allowed a remote attacker to potentially perform out of bounds memory access via a crafted HTML page. This vulnerability relates to an electron component.

Remediation

Upgrade electron to version 10.4.2, 11.4.1 or higher.

References

high severity

Arbitrary File Write

  • Vulnerable module: tar
  • Introduced through: connect-sqlite3@0.9.13

Detailed paths

  • Introduced through: vanguard-core@0.1.27 connect-sqlite3@0.9.13 sqlite3@5.0.2 node-gyp@3.8.0 tar@2.2.2

Overview

tar is a full-featured Tar for Node.js.

Affected versions of this package are vulnerable to Arbitrary File Write. node-tar aims to guarantee that any file whose location would be modified by a symbolic link is not extracted. This is, in part, achieved by ensuring that extracted directories are not symlinks. Additionally, in order to prevent unnecessary stat calls to determine whether a given path is a directory, paths are cached when directories are created.

This logic was insufficient when extracting tar files that contained both a directory and a symlink with the same name as the directory, where the symlink and directory names in the archive entry used backslashes as a path separator on posix systems. The cache checking logic used both \ and / characters as path separators. However, \ is a valid filename character on posix systems.

By first creating a directory, and then replacing that directory with a symlink, it is possible to bypass node-tar symlink checks on directories, essentially allowing an untrusted tar file to symlink into an arbitrary location. This can lead to extracting arbitrary files into that location, thus allowing arbitrary file creation and overwrite.

Additionally, a similar confusion could arise on case-insensitive filesystems. If a tar archive contained a directory at FOO, followed by a symbolic link named foo, then on case-insensitive file systems, the creation of the symbolic link would remove the directory from the filesystem, but not from the internal directory cache, as it would not be treated as a cache hit. A subsequent file entry within the FOO directory would then be placed in the target of the symbolic link, thinking that the directory had already been created.

Remediation

Upgrade tar to version 6.1.7, 5.0.8, 4.4.16 or higher.

References

high severity

Arbitrary File Write

  • Vulnerable module: tar
  • Introduced through: connect-sqlite3@0.9.13

Detailed paths

  • Introduced through: vanguard-core@0.1.27 connect-sqlite3@0.9.13 sqlite3@5.0.2 node-gyp@3.8.0 tar@2.2.2

Overview

tar is a full-featured Tar for Node.js.

Affected versions of this package are vulnerable to Arbitrary File Write. node-tar aims to guarantee that any file whose location would be modified by a symbolic link is not extracted. This is, in part, achieved by ensuring that extracted directories are not symlinks. Additionally, in order to prevent unnecessary stat calls to determine whether a given path is a directory, paths are cached when directories are created.

This logic is insufficient when extracting tar files that contain two directories and a symlink with names containing unicode values that normalized to the same value. Additionally, on Windows systems, long path portions would resolve to the same file system entities as their 8.3 "short path" counterparts. A specially crafted tar archive can include directories with two forms of the path that resolve to the same file system entity, followed by a symbolic link with a name in the first form, lastly followed by a file using the second form. This leads to bypassing node-tar symlink checks on directories, essentially allowing an untrusted tar file to symlink into an arbitrary location and extracting arbitrary files into that location.

Remediation

Upgrade tar to version 6.1.9, 5.0.10, 4.4.18 or higher.

References

high severity

Arbitrary File Write

  • Vulnerable module: tar
  • Introduced through: connect-sqlite3@0.9.13

Detailed paths

  • Introduced through: vanguard-core@0.1.27 connect-sqlite3@0.9.13 sqlite3@5.0.2 node-gyp@3.8.0 tar@2.2.2

Overview

tar is a full-featured Tar for Node.js.

Affected versions of this package are vulnerable to Arbitrary File Write. node-tar aims to guarantee that any file whose location would be outside of the extraction target directory is not extracted. This is, in part, accomplished by sanitizing absolute paths of entries within the archive, skipping archive entries that contain .. path portions, and resolving the sanitized paths against the extraction target directory.

This logic is insufficient on Windows systems when extracting tar files that contain a path that is not an absolute path, but specify a drive letter different from the extraction target, such as C:some\path. If the drive letter does not match the extraction target, for example D:\extraction\dir, then the result of path.resolve(extractionDirectory, entryPath) resolves against the current working directory on the C: drive, rather than the extraction target directory.

Additionally, a .. portion of the path can occur immediately after the drive letter, such as C:../foo, and is not properly sanitized by the logic that checks for .. within the normalized and split portions of the path.

Note: This only affects users of node-tar on Windows systems.

Remediation

Upgrade tar to version 6.1.9, 5.0.10, 4.4.18 or higher.

References

high severity

Arbitrary Code Execution

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@2.0.17.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Arbitrary Code Execution. Opening a BrowserView with sandbox: true or nativeWindowOpen: true and nodeIntegration: false results in a webContents where window.open() can be called and the newly opened child will have nodeIntegration enabled.

Remediation

Upgrade electron to version 2.0.17, 3.0.15, 3.1.3, 4.0.4, 5.0.0-beta.2 or higher.

If for some reason you are unable to upgrade your Electron version, you can mitigate this issue by disabling all child web contents: view.webContents.on('-add-new-contents', e => e.preventDefault());

References

high severity

Site Isolation Bypass

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@7.2.2.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Site Isolation Bypass. parent_execution_origin_ is provided from parent's RenderFrameHostImpl::last_committed_origin_ that is set during navigation commit. Worker creation IPC from the renderer to browser could race with navigation commit, and could see the wrong last committed origin.

Remediation

Upgrade electron to version 7.2.2, 8.2.1 or higher.

References

high severity

Use After Free

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@9.4.4.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Use After Free. Since JavaScript may detach the underlying buffers, they need to be checked to ensure they're still valid before using them for decoding.

Remediation

Upgrade electron to version 10.2.0, 9.4.4 or higher.

References

high severity

Use After Free

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@6.1.10.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Use After Free. An AudioContext is considered to have activity if it's not closed. Previously, suspended contexts were considered has having no activity, but that's not quite true since the context can be resumed at any time after. This would allow contexts to be collected prematurely even though the context was resumed. This causes the audio thread to access objects that are possibly deleted.

Remediation

Upgrade electron to version 6.1.10, 7.2.2, 8.0.0-beta.6 or higher.

References

high severity

Arbitrary File Overwrite

  • Vulnerable module: tar
  • Introduced through: connect-sqlite3@0.9.13

Detailed paths

  • Introduced through: vanguard-core@0.1.27 connect-sqlite3@0.9.13 sqlite3@5.0.2 node-gyp@3.8.0 tar@2.2.2

Overview

tar is a full-featured Tar for Node.js.

Affected versions of this package are vulnerable to Arbitrary File Overwrite. This is due to insufficient symlink protection. node-tar aims to guarantee that any file whose location would be modified by a symbolic link is not extracted. This is, in part, achieved by ensuring that extracted directories are not symlinks. Additionally, in order to prevent unnecessary stat calls to determine whether a given path is a directory, paths are cached when directories are created.

This logic is insufficient when extracting tar files that contain both a directory and a symlink with the same name as the directory. This order of operations results in the directory being created and added to the node-tar directory cache. When a directory is present in the directory cache, subsequent calls to mkdir for that directory are skipped. However, this is also where node-tar checks for symlinks occur. By first creating a directory, and then replacing that directory with a symlink, it is possible to bypass node-tar symlink checks on directories, essentially allowing an untrusted tar file to symlink into an arbitrary location and subsequently extracting arbitrary files into that location.

Remediation

Upgrade tar to version 3.2.3, 4.4.15, 5.0.7, 6.1.2 or higher.

References

high severity

Arbitrary File Overwrite

  • Vulnerable module: tar
  • Introduced through: connect-sqlite3@0.9.13

Detailed paths

  • Introduced through: vanguard-core@0.1.27 connect-sqlite3@0.9.13 sqlite3@5.0.2 node-gyp@3.8.0 tar@2.2.2

Overview

tar is a full-featured Tar for Node.js.

Affected versions of this package are vulnerable to Arbitrary File Overwrite. This is due to insufficient absolute path sanitization.

node-tar aims to prevent extraction of absolute file paths by turning absolute paths into relative paths when the preservePaths flag is not set to true. This is achieved by stripping the absolute path root from any absolute file paths contained in a tar file. For example, the path /home/user/.bashrc would turn into home/user/.bashrc.

This logic is insufficient when file paths contain repeated path roots such as ////home/user/.bashrc. node-tar only strips a single path root from such paths. When given an absolute file path with repeating path roots, the resulting path (e.g. ///home/user/.bashrc) still resolves to an absolute path.

Remediation

Upgrade tar to version 3.2.2, 4.4.14, 5.0.6, 6.1.1 or higher.

References

high severity

Insecure Defaults

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@10.4.1.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Insecure Defaults. Insufficient policy enforcement in the File System API of chromium allows a remote attacker to bypass filesystem restrictions via a crafted HTML page.

Remediation

Upgrade electron to version 10.4.1, 11.4.1 or higher.

References

high severity

Arbitrary Code Execution

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@1.8.2.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Arbitrary Code Execution. It appears to be exploitable via the victim opening an electron protocol handler in their browser.

This issue is due to an incomplete fix for CVE-2018-1000006, specifically the black list used was not case insensitive allowing an attacker to potentially bypass it.

Remediation

Upgrade electron to version 1.8.2-beta.5 or higher.

References

high severity

Privilege Escalation

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@1.3.1.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Privilege Escalation. It allowed local users to gain privileges via a Trojan horse Node.js module in a parent directory of a directory named on a require line.

Remediation

Upgrade electron to version 0.33.5 or higher.

References

high severity

Privilege Escalation

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@7.2.4.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Privilege Escalation. This is a context isolation bypass, meaning that code running in the main world context in the renderer can reach into the isolated Electron context and perform privileged actions.

##Note: Only apps using contextIsolation are affected.

Remediation

Upgrade electron to version 7.2.4, 8.2.4 or higher.

References

high severity

Privilege Escalation

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@7.2.4.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Privilege Escalation. This is a context isolation bypass, meaning that code running in the main world context in the renderer can reach into the isolated Electron context and perform privileged actions.

##Note: Only apps using both contextIsolation and contextBridge are affected.

Remediation

Upgrade electron to version 7.2.4, 8.2.4 or higher.

References

high severity

Privilege Escalation

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@6.1.11.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Privilege Escalation. This is a context isolation bypass, meaning that code running in the main world context in the renderer can reach into the isolated Electron context and perform privileged actions.

##Note: Only apps using contextIsolation are affected.

Remediation

Upgrade electron to version 6.1.11, 7.2.4, 8.2.4 or higher.

References

high severity

Heap-based Buffer Overflow

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@8.5.3.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Heap-based Buffer Overflow in Freetype.

Remediation

Upgrade electron to version 8.5.3, 9.3.3, 10.1.5 or higher.

References

high severity

Heap-based Buffer Overflow

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@10.4.4.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Heap-based Buffer Overflow via V8.

Remediation

Upgrade electron to version 10.4.4, 11.4.4, 12.0.6 or higher.

References

high severity

Out-of-bounds Read

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@9.4.1.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Out-of-bounds Read. An unknown vunerability exists in Chrome which affects electron.

Remediation

Upgrade electron to version 9.4.1, 10.3.2 or higher.

References

high severity

Uninitialized Memory Exposure

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@1.6.1.

Overview

electron is a framework for creating native applications with web technologies like JavaScript, HTML, and CSS. It takes care of the hard parts so you can focus on the core of your application.

Affected versions of the package are vulnerable to Uninitialized Memory Exposure. The Buffer class in Node.js is available as global, even if the nodeintegration attribute is not added. This could result in concatenation of uninitialized memory to the buffer collection.

This is a result of unobstructed use of the Buffer constructor, whose insecure default constructor increases the odds of memory leakage.

Remediation

Upgrade electron to version 1.6.1 or higher. Note This is vulnerable only for Node <=4

References

high severity

Use After Free

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@6.1.10.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Use After Free. FileChooserImpl can outlive ListenerProxy leading to a crash.

Remediation

Upgrade electron to version 6.1.10, 7.2.2, 8.2.0 or higher.

References

high severity

Use After Free

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@6.1.10.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Use After Free. Initialize() could potentially run twice in MojoVideoEncodeAcceleratorService.

Remediation

Upgrade electron to version 6.1.10, 7.2.2, 8.2.1 or higher.

References

high severity

Regular Expression Denial of Service (ReDoS)

  • Vulnerable module: fresh
  • Introduced through: express@3.4.8

Detailed paths

  • Introduced through: vanguard-core@0.1.27 express@3.4.8 fresh@0.2.0
    Remediation: Upgrade to express@4.15.5.
  • Introduced through: vanguard-core@0.1.27 express@3.4.8 send@0.1.4 fresh@0.2.0
    Remediation: Upgrade to express@4.15.5.
  • Introduced through: vanguard-core@0.1.27 express@3.4.8 connect@2.12.0 fresh@0.2.0
    Remediation: Upgrade to express@4.0.0.
  • Introduced through: vanguard-core@0.1.27 express@3.4.8 connect@2.12.0 send@0.1.4 fresh@0.2.0
    Remediation: Upgrade to express@4.0.0.

Overview

fresh is HTTP response freshness testing.

Affected versions of this package are vulnerable to Regular expression Denial of Service (ReDoS) attacks. A Regular Expression (/ *, */) was used for parsing HTTP headers and take about 2 seconds matching time for 50k characters.

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.

The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.

Let’s take the following regular expression as an example:

regex = /A(B|C+)+D/

This regular expression accomplishes the following:

  • A The string must start with the letter 'A'
  • (B|C+)+ The string must then follow the letter A with either the letter 'B' or some number of occurrences of the letter 'C' (the + matches one or more times). The + at the end of this section states that we can look for one or more matches of this section.
  • D Finally, we ensure this section of the string ends with a 'D'

The expression would match inputs such as ABBD, ABCCCCD, ABCBCCCD and ACCCCCD

It most cases, it doesn't take very long for a regex engine to find a match:

$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
0.04s user 0.01s system 95% cpu 0.052 total

$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
1.79s user 0.02s system 99% cpu 1.812 total

The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.

Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.

Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:

  1. CCC
  2. CC+C
  3. C+CC
  4. C+C+C.

The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.

From there, the number of steps the engine must use to validate a string just continues to grow.

String Number of C's Number of steps
ACCCX 3 38
ACCCCX 4 71
ACCCCCX 5 136
ACCCCCCCCCCCCCCX 14 65,553

By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.

Remediation

Upgrade fresh to version 0.5.2 or higher.

References

high severity

Regular Expression Denial of Service (ReDoS)

  • Vulnerable module: negotiator
  • Introduced through: express@3.4.8

Detailed paths

  • Introduced through: vanguard-core@0.1.27 express@3.4.8 connect@2.12.0 negotiator@0.3.0
    Remediation: Upgrade to express@4.0.0.

Overview

negotiator is an HTTP content negotiator for Node.js.

Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) when parsing Accept-Language http header.

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.

The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.

Let’s take the following regular expression as an example:

regex = /A(B|C+)+D/

This regular expression accomplishes the following:

  • A The string must start with the letter 'A'
  • (B|C+)+ The string must then follow the letter A with either the letter 'B' or some number of occurrences of the letter 'C' (the + matches one or more times). The + at the end of this section states that we can look for one or more matches of this section.
  • D Finally, we ensure this section of the string ends with a 'D'

The expression would match inputs such as ABBD, ABCCCCD, ABCBCCCD and ACCCCCD

It most cases, it doesn't take very long for a regex engine to find a match:

$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
0.04s user 0.01s system 95% cpu 0.052 total

$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
1.79s user 0.02s system 99% cpu 1.812 total

The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.

Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.

Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:

  1. CCC
  2. CC+C
  3. C+CC
  4. C+C+C.

The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.

From there, the number of steps the engine must use to validate a string just continues to grow.

String Number of C's Number of steps
ACCCX 3 38
ACCCCX 4 71
ACCCCCX 5 136
ACCCCCCCCCCCCCCX 14 65,553

By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.

Remediation

Upgrade negotiator to version 0.6.1 or higher.

References

high severity

Denial of Service (DoS)

  • Vulnerable module: qs
  • Introduced through: express@3.4.8

Detailed paths

  • Introduced through: vanguard-core@0.1.27 express@3.4.8 connect@2.12.0 qs@0.6.6
    Remediation: Upgrade to express@3.16.0.

Overview

qs is a querystring parser that supports nesting and arrays, with a depth limit.

Affected versions of this package are vulnerable to Denial of Service (DoS). During parsing, the qs module may create a sparse area (an array where no elements are filled), and grow that array to the necessary size based on the indices used on it. An attacker can specify a high index value in a query string, thus making the server allocate a respectively big array. Truly large values can cause the server to run out of memory and cause it to crash - thus enabling a Denial-of-Service attack.

Remediation

Upgrade qs to version 1.0.0 or higher.

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.

Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.

One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.

When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.

Two common types of DoS vulnerabilities:

  • High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.

  • Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package

References

high severity

Prototype Override Protection Bypass

  • Vulnerable module: qs
  • Introduced through: express@3.4.8

Detailed paths

  • Introduced through: vanguard-core@0.1.27 express@3.4.8 connect@2.12.0 qs@0.6.6
    Remediation: Upgrade to express@4.0.0.

Overview

qs is a querystring parser that supports nesting and arrays, with a depth limit.

Affected versions of this package are vulnerable to Prototype Override Protection Bypass. By default qs protects against attacks that attempt to overwrite an object's existing prototype properties, such as toString(), hasOwnProperty(),etc.

From qs documentation:

By default parameters that would overwrite properties on the object prototype are ignored, if you wish to keep the data from those fields either use plainObjects as mentioned above, or set allowPrototypes to true which will allow user input to overwrite those properties. WARNING It is generally a bad idea to enable this option as it can cause problems when attempting to use the properties that have been overwritten. Always be careful with this option.

Overwriting these properties can impact application logic, potentially allowing attackers to work around security controls, modify data, make the application unstable and more.

In versions of the package affected by this vulnerability, it is possible to circumvent this protection and overwrite prototype properties and functions by prefixing the name of the parameter with [ or ]. e.g. qs.parse("]=toString") will return {toString = true}, as a result, calling toString() on the object will throw an exception.

Example:

qs.parse('toString=foo', { allowPrototypes: false })
// {}

qs.parse("]=toString", { allowPrototypes: false })
// {toString = true} <== prototype overwritten

For more information, you can check out our blog.

Disclosure Timeline

  • February 13th, 2017 - Reported the issue to package owner.
  • February 13th, 2017 - Issue acknowledged by package owner.
  • February 16th, 2017 - Partial fix released in versions 6.0.3, 6.1.1, 6.2.2, 6.3.1.
  • March 6th, 2017 - Final fix released in versions 6.4.0,6.3.2, 6.2.3, 6.1.2 and 6.0.4

    Remediation

    Upgrade qs to version 6.0.4, 6.1.2, 6.2.3, 6.3.2 or higher.

    References

  • GitHub Commit
  • GitHub Issue

high severity

Out-of-bounds Read

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@10.4.4.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Out-of-bounds Read via the IPC in chromium.

Remediation

Upgrade electron to version 11.4.4, 10.4.4 or higher.

References

high severity

Arbitrary Code Execution

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@5.0.0.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Arbitrary Code Execution due to Node being enabled in a webview because the default values of nodeIntegration and webviewTag were set to true when they where undefined by a user. The fix allows users to prevent Node and webview being enabled, when undefined, by setting the default values of nodeIntegration and webviewTag to false.

Remediation

Upgrade electron to version 5.0.0-beta.1 or higher.

References

high severity

Buffer Overflow

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@12.2.0.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Buffer Overflow in ANGLE.

Remediation

Upgrade electron to version 13.5.0, 12.2.0 or higher.

References

high severity

Heap-based Buffer Overflow

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@10.4.7.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Heap-based Buffer Overflow in Reader Mode.

Remediation

Upgrade electron to version 12.0.10, 11.4.8, 10.4.7 or higher.

References

high severity

Heap-based Buffer Overflow

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@10.4.7.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Heap-based Buffer Overflow in History.

Remediation

Upgrade electron to version 12.0.10, 11.4.8, 10.4.7 or higher.

References

high severity

Heap-based Buffer Overflow

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@10.4.7.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Heap-based Buffer Overflow in Media Feeds.

Remediation

Upgrade electron to version 12.0.10, 11.4.8, 10.4.7 or higher.

References

high severity

Heap-based Buffer Overflow

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@13.5.2.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Heap-based Buffer Overflow via the Blink module in Chromium.

Remediation

Upgrade electron to version 14.2.0, 13.5.2 or higher.

References

high severity

Improper Validation

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@9.4.4.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Improper Validation. The value of a node was accessed without prior HasValue check. With WebAssembly this node is not guaranteed to be a value.

Remediation

Upgrade electron to version 10.1.6, 9.4.4 or higher.

References

high severity

Insufficient Validation

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@9.4.0.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Insufficient Validation in V8.

Remediation

Upgrade electron to version 9.4.0, 10.2.0 or higher.

References

high severity

Insufficient Validation

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@9.4.2.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Insufficient Validation via an unknown issue in chromium.

Remediation

Upgrade electron to version 9.4.2, 10.3.1, 11.2.2 or higher.

References

high severity

Out-of-Bounds

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@12.2.0.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Out-of-Bounds in ANGLE.

Remediation

Upgrade electron to version 13.5.0, 12.2.0 or higher.

References

high severity

Out-of-bounds Read

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@6.1.10.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Out-of-bounds Read. The input to sctp_load_addresses_from_init is verified by calling sctp_arethere_unrecognized_parameters, however there is a difference in how these functions handle parameter bounds. The function sctp_arethere_unrecognized_parameters does not process a parameter that is partially outside of the limit of the chunk, meanwhile, sctp_load_addresses_from_init will continue processing until a parameter that is entirely outside of the chunk occurs.

This means that the last parameter of a chunk is not always verified, which can lead to parameters with very short plen values being processed by sctp_load_addresses_from_init. This can lead to out-of-bounds reads whenever the plen is subtracted from the header len.

Remediation

Upgrade electron to version 6.1.10, 7.2.2, 8.2.0 or higher.

References

high severity

Race Condition

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@10.4.7.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Race Condition in Aura.

Remediation

Upgrade electron to version 12.0.10, 11.4.8, 10.4.7 or higher.

References

medium severity

Arbitrary File Read

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@7.2.4.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Arbitrary File Read. It allows arbitrary local file read by defining unsafe window options on a child window opened via window.open.

Remediation

Upgrade electron to version 7.2.4, 8.2.4 or higher.

References

medium severity

Use After Free

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@6.1.10.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Use After Free. The rendering_orphan_handlers_ and deletable_orphan_handlers_ handlers can hold references to the context after BaseAudioContext is destroyed.

Remediation

Upgrade electron to version 6.1.10, 7.2.2, 8.2.1 or higher.

References

medium severity

Access Restriction Bypass

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@10.4.3.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Access Restriction Bypass. Inappropriate implementation in Referrer in Google Chrome prior to 89.0.4389.72 allowed a remote attacker to bypass navigation restrictions via a crafted HTML page. This vulnerability relates to an electron component.

Remediation

Upgrade electron to version 10.4.3, 11.4.1 or higher.

References

medium severity

Cross-site Scripting (XSS)

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@1.6.8.

Overview

electron is a framework for creating native applications with web technologies like JavaScript, HTML, and CSS. It takes care of the hard parts so you can focus on the core of your application.

Affected versions of this package are vulnerable to Cross-site Scripting (XSS) attacks. A new window opened from within a window that had javascript disabled, would have javascript enabled by default.

Details

A cross-site scripting attack occurs when the attacker tricks a legitimate web-based application or site to accept a request as originating from a trusted source.

This is done by escaping the context of the web application; the web application then delivers that data to its users along with other trusted dynamic content, without validating it. The browser unknowingly executes malicious script on the client side (through client-side languages; usually JavaScript or HTML) in order to perform actions that are otherwise typically blocked by the browser’s Same Origin Policy.

ֿInjecting malicious code is the most prevalent manner by which XSS is exploited; for this reason, escaping characters in order to prevent this manipulation is the top method for securing code against this vulnerability.

Escaping means that the application is coded to mark key characters, and particularly key characters included in user input, to prevent those characters from being interpreted in a dangerous context. For example, in HTML, < can be coded as &lt; and > can be coded as &gt; in order to be interpreted and displayed as themselves in text, while within the code itself, they are used for HTML tags. If malicious content is injected into an application that escapes special characters and that malicious content uses < and > as HTML tags, those characters are nonetheless not interpreted as HTML tags by the browser if they’ve been correctly escaped in the application code and in this way the attempted attack is diverted.

The most prominent use of XSS is to steal cookies (source: OWASP HttpOnly) and hijack user sessions, but XSS exploits have been used to expose sensitive information, enable access to privileged services and functionality and deliver malware.

Types of attacks

There are a few methods by which XSS can be manipulated:

Type Origin Description
Stored Server The malicious code is inserted in the application (usually as a link) by the attacker. The code is activated every time a user clicks the link.
Reflected Server The attacker delivers a malicious link externally from the vulnerable web site application to a user. When clicked, malicious code is sent to the vulnerable web site, which reflects the attack back to the user’s browser.
DOM-based Client The attacker forces the user’s browser to render a malicious page. The data in the page itself delivers the cross-site scripting data.
Mutated The attacker injects code that appears safe, but is then rewritten and modified by the browser, while parsing the markup. An example is rebalancing unclosed quotation marks or even adding quotation marks to unquoted parameters.

Affected environments

The following environments are susceptible to an XSS attack:

  • Web servers
  • Application servers
  • Web application environments

How to prevent

This section describes the top best practices designed to specifically protect your code:

  • Sanitize data input in an HTTP request before reflecting it back, ensuring all data is validated, filtered or escaped before echoing anything back to the user, such as the values of query parameters during searches.
  • Convert special characters such as ?, &, /, <, > and spaces to their respective HTML or URL encoded equivalents.
  • Give users the option to disable client-side scripts.
  • Redirect invalid requests.
  • Detect simultaneous logins, including those from two separate IP addresses, and invalidate those sessions.
  • Use and enforce a Content Security Policy (source: Wikipedia) to disable any features that might be manipulated for an XSS attack.
  • Read the documentation for any of the libraries referenced in your code to understand which elements allow for embedded HTML.

Remediation

Upgrade electron to version 1.6.8 or higher.

References

medium severity

Cross-site Scripting (XSS)

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@1.6.8.

Overview

electron is a framework for creating native applications with web technologies like JavaScript, HTML, and CSS. It takes care of the hard parts so you can focus on the core of your application.

Affected versions of this package are vulnerable to Cross-site Scripting (XSS) attacks.

Details

A cross-site scripting attack occurs when the attacker tricks a legitimate web-based application or site to accept a request as originating from a trusted source.

This is done by escaping the context of the web application; the web application then delivers that data to its users along with other trusted dynamic content, without validating it. The browser unknowingly executes malicious script on the client side (through client-side languages; usually JavaScript or HTML) in order to perform actions that are otherwise typically blocked by the browser’s Same Origin Policy.

ֿInjecting malicious code is the most prevalent manner by which XSS is exploited; for this reason, escaping characters in order to prevent this manipulation is the top method for securing code against this vulnerability.

Escaping means that the application is coded to mark key characters, and particularly key characters included in user input, to prevent those characters from being interpreted in a dangerous context. For example, in HTML, < can be coded as &lt; and > can be coded as &gt; in order to be interpreted and displayed as themselves in text, while within the code itself, they are used for HTML tags. If malicious content is injected into an application that escapes special characters and that malicious content uses < and > as HTML tags, those characters are nonetheless not interpreted as HTML tags by the browser if they’ve been correctly escaped in the application code and in this way the attempted attack is diverted.

The most prominent use of XSS is to steal cookies (source: OWASP HttpOnly) and hijack user sessions, but XSS exploits have been used to expose sensitive information, enable access to privileged services and functionality and deliver malware.

Types of attacks

There are a few methods by which XSS can be manipulated:

Type Origin Description
Stored Server The malicious code is inserted in the application (usually as a link) by the attacker. The code is activated every time a user clicks the link.
Reflected Server The attacker delivers a malicious link externally from the vulnerable web site application to a user. When clicked, malicious code is sent to the vulnerable web site, which reflects the attack back to the user’s browser.
DOM-based Client The attacker forces the user’s browser to render a malicious page. The data in the page itself delivers the cross-site scripting data.
Mutated The attacker injects code that appears safe, but is then rewritten and modified by the browser, while parsing the markup. An example is rebalancing unclosed quotation marks or even adding quotation marks to unquoted parameters.

Affected environments

The following environments are susceptible to an XSS attack:

  • Web servers
  • Application servers
  • Web application environments

How to prevent

This section describes the top best practices designed to specifically protect your code:

  • Sanitize data input in an HTTP request before reflecting it back, ensuring all data is validated, filtered or escaped before echoing anything back to the user, such as the values of query parameters during searches.
  • Convert special characters such as ?, &, /, <, > and spaces to their respective HTML or URL encoded equivalents.
  • Give users the option to disable client-side scripts.
  • Redirect invalid requests.
  • Detect simultaneous logins, including those from two separate IP addresses, and invalidate those sessions.
  • Use and enforce a Content Security Policy (source: Wikipedia) to disable any features that might be manipulated for an XSS attack.
  • Read the documentation for any of the libraries referenced in your code to understand which elements allow for embedded HTML.

Remediation

Upgrade electron to version 1.6.8 or higher.

References

medium severity
new

Domain Spoofing

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@16.0.0.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Domain Spoofing via a crafted HTML page as a result of inappropriate implementation in navigation in Google Chrome.

Remediation

Upgrade electron to version 16.0.0 or higher.

References

medium severity

Heap-based Buffer Overflow

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@11.4.11.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Heap-based Buffer Overflow in WebGL via Chrome. This allows a remote attacker to potentially exploit heap corruption via a crafted HTML page.

Remediation

Upgrade electron to version 13.1.8, 12.0.16, 11.4.11 or higher.

References

medium severity

Improper Input Validation

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@9.4.4.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Improper Input Validation via the File System API.

Remediation

Upgrade electron to version 11.2.1, 9.4.4 or higher.

References

medium severity

Improper Input Validation

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@12.2.1.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Improper Input Validation. Insufficient validation exist in the svg painting code which may access a content-visibility locked element via an svg reference.

Remediation

Upgrade electron to version 14.1.0, 13.5.1, 12.2.1 or higher.

References

medium severity
new

Inappropriate Implementation

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@13.6.6.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Inappropriate Implementation via cache in Google Chrome. This allows a remote attacker to leak cross-origin data via a crafted HTML page.

Remediation

Upgrade electron to version 13.6.6, 14.2.2, 15.3.3 or higher.

References

medium severity

Information Exposure

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@9.4.1.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Information Exposure. When a BigInt is right-shifted the backing store is not properly cleared, allowing uninitialized memory to be read.

Remediation

Upgrade electron to version 9.4.1, 10.3.2 or higher.

References

medium severity

Information Exposure

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@12.2.2.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Information Exposure via the core module in Chromium.

Remediation

Upgrade electron to version 14.2.0, 13.5.2, 12.2.2 or higher.

References

medium severity

Denial of Service (DoS)

  • Vulnerable module: qs
  • Introduced through: express@3.4.8

Detailed paths

  • Introduced through: vanguard-core@0.1.27 express@3.4.8 connect@2.12.0 qs@0.6.6
    Remediation: Upgrade to express@3.16.0.

Overview

qs is a querystring parser that supports nesting and arrays, with a depth limit.

Affected versions of this package are vulnerable to Denial of Service (DoS). When parsing a string representing a deeply nested object, qs will block the event loop for long periods of time. Such a delay may hold up the server's resources, keeping it from processing other requests in the meantime, thus enabling a Denial-of-Service attack.

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.

The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.

Let’s take the following regular expression as an example:

regex = /A(B|C+)+D/

This regular expression accomplishes the following:

  • A The string must start with the letter 'A'
  • (B|C+)+ The string must then follow the letter A with either the letter 'B' or some number of occurrences of the letter 'C' (the + matches one or more times). The + at the end of this section states that we can look for one or more matches of this section.
  • D Finally, we ensure this section of the string ends with a 'D'

The expression would match inputs such as ABBD, ABCCCCD, ABCBCCCD and ACCCCCD

It most cases, it doesn't take very long for a regex engine to find a match:

$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
0.04s user 0.01s system 95% cpu 0.052 total

$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
1.79s user 0.02s system 99% cpu 1.812 total

The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.

Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.

Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:

  1. CCC
  2. CC+C
  3. C+CC
  4. C+C+C.

The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.

From there, the number of steps the engine must use to validate a string just continues to grow.

String Number of C's Number of steps
ACCCX 3 38
ACCCCX 4 71
ACCCCCX 5 136
ACCCCCCCCCCCCCCX 14 65,553

By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.

Remediation

Upgrade qs to version 1.0.0 or higher.

References

medium severity

Non-Constant Time String Comparison

  • Vulnerable module: cookie-signature
  • Introduced through: express@3.4.8

Detailed paths

  • Introduced through: vanguard-core@0.1.27 express@3.4.8 cookie-signature@1.0.1
    Remediation: Upgrade to express@3.12.1.
  • Introduced through: vanguard-core@0.1.27 express@3.4.8 connect@2.12.0 cookie-signature@1.0.1
    Remediation: Upgrade to express@3.12.1.

Overview

'cookie-signature' is a library for signing cookies.

Versions before 1.0.4 of the library use the built-in string comparison mechanism, ===, and not a time constant string comparison. As a result, the comparison will fail faster when the first characters in the token are incorrect. An attacker can use this difference to perform a timing attack, essentially allowing them to guess the secret one character at a time.

You can read more about timing attacks in Node.js on the Snyk blog: https://snyk.io/blog/node-js-timing-attack-ccc-ctf/

Remediation

Upgrade to 1.0.4 or greater.

References

medium severity

Use After Free

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@11.4.10.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Use After Free in Network service.

Remediation

Upgrade electron to version 12.0.13, 11.4.10 or higher.

References

medium severity

Use After Free

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@11.4.11.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Use After Free via sqlite. This can allow a remote attacker to potentially exploit heap corruption via a crafted HTML page.

Remediation

Upgrade electron to version 13.1.8, 12.0.16, 11.4.11 or higher.

References

medium severity

Buffer Underflow

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@6.1.10.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Buffer Underflow. Since there may be multiple instance of DWriteFontProxyImpl instantiated for multiple RenderProcessHosts, and DWriteFontProxyImpl::GetUniqueNameLookupTable may access DWriteFontLookupTableBuilder::QueueShareMemoryRegionWhenReady from separate threads, there may be race conditions around the pending_callbacks_ member of DWriteFontLookupTableBuilder.

Remediation

Upgrade electron to version 6.1.10, 7.2.2, 8.2.0 or higher.

References

medium severity
new

Inappropriate Implementation

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@14.2.2.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Inappropriate Implementation via service workers in Google Chrome. This allows a remote attacker who had compromised the renderer process to bypass site isolation via a crafted HTML page.

Remediation

Upgrade electron to version 14.2.2, 15.3.3 or higher.

References

medium severity

Sandbox Bypass

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@12.2.2.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Sandbox Bypass via chromium, due to a child process's delayed integrity level not being set correctly.

Remediation

Upgrade electron to version 12.2.2, 13.5.2, 14.2.0 or higher.

References

medium severity

Arbitrary Code Injection

  • Vulnerable module: underscore
  • Introduced through: underscore@1.5.2

Detailed paths

  • Introduced through: vanguard-core@0.1.27 underscore@1.5.2
    Remediation: Upgrade to underscore@1.12.1.

Overview

underscore is a JavaScript's functional programming helper library.

Affected versions of this package are vulnerable to Arbitrary Code Injection via the template function, particularly when the variable option is taken from _.templateSettings as it is not sanitized.

PoC

const _ = require('underscore');
_.templateSettings.variable = "a = this.process.mainModule.require('child_process').execSync('touch HELLO')";
const t = _.template("")();

Remediation

Upgrade underscore to version 1.13.0-2, 1.12.1 or higher.

References

medium severity

Cross-site Scripting (XSS)

  • Vulnerable module: express
  • Introduced through: express@3.4.8

Detailed paths

  • Introduced through: vanguard-core@0.1.27 express@3.4.8
    Remediation: Upgrade to express@3.11.0.

Overview

express is a minimalist web framework.

Affected versions of this package do not enforce the user's browser to set a specific charset in the content-type header while displaying 400 level response messages. This could be used by remote attackers to perform a cross-site scripting attack, by using non-standard encodings like UTF-7.

Details

A cross-site scripting attack occurs when the attacker tricks a legitimate web-based application or site to accept a request as originating from a trusted source.

This is done by escaping the context of the web application; the web application then delivers that data to its users along with other trusted dynamic content, without validating it. The browser unknowingly executes malicious script on the client side (through client-side languages; usually JavaScript or HTML) in order to perform actions that are otherwise typically blocked by the browser’s Same Origin Policy.

ֿInjecting malicious code is the most prevalent manner by which XSS is exploited; for this reason, escaping characters in order to prevent this manipulation is the top method for securing code against this vulnerability.

Escaping means that the application is coded to mark key characters, and particularly key characters included in user input, to prevent those characters from being interpreted in a dangerous context. For example, in HTML, < can be coded as &lt; and > can be coded as &gt; in order to be interpreted and displayed as themselves in text, while within the code itself, they are used for HTML tags. If malicious content is injected into an application that escapes special characters and that malicious content uses < and > as HTML tags, those characters are nonetheless not interpreted as HTML tags by the browser if they’ve been correctly escaped in the application code and in this way the attempted attack is diverted.

The most prominent use of XSS is to steal cookies (source: OWASP HttpOnly) and hijack user sessions, but XSS exploits have been used to expose sensitive information, enable access to privileged services and functionality and deliver malware.

Types of attacks

There are a few methods by which XSS can be manipulated:

Type Origin Description
Stored Server The malicious code is inserted in the application (usually as a link) by the attacker. The code is activated every time a user clicks the link.
Reflected Server The attacker delivers a malicious link externally from the vulnerable web site application to a user. When clicked, malicious code is sent to the vulnerable web site, which reflects the attack back to the user’s browser.
DOM-based Client The attacker forces the user’s browser to render a malicious page. The data in the page itself delivers the cross-site scripting data.
Mutated The attacker injects code that appears safe, but is then rewritten and modified by the browser, while parsing the markup. An example is rebalancing unclosed quotation marks or even adding quotation marks to unquoted parameters.

Affected environments

The following environments are susceptible to an XSS attack:

  • Web servers
  • Application servers
  • Web application environments

How to prevent

This section describes the top best practices designed to specifically protect your code:

  • Sanitize data input in an HTTP request before reflecting it back, ensuring all data is validated, filtered or escaped before echoing anything back to the user, such as the values of query parameters during searches.
  • Convert special characters such as ?, &, /, <, > and spaces to their respective HTML or URL encoded equivalents.
  • Give users the option to disable client-side scripts.
  • Redirect invalid requests.
  • Detect simultaneous logins, including those from two separate IP addresses, and invalidate those sessions.
  • Use and enforce a Content Security Policy (source: Wikipedia) to disable any features that might be manipulated for an XSS attack.
  • Read the documentation for any of the libraries referenced in your code to understand which elements allow for embedded HTML.

Recommendations

Update express to 3.11.0, 4.5.0 or higher.

References

medium severity

Denial of Service (DoS)

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@1.6.8.

Overview

electron is a framework for creating native applications with web technologies like JavaScript, HTML, and CSS. It takes care of the hard parts so you can focus on the core of your application.

Affected versions of the package are vulnerable to Denial of Service (DoS). Valid frame names passed into window.open would throw errors and cause the service to crash.

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.

Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.

One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.

When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.

Two common types of DoS vulnerabilities:

  • High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.

  • Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package

Remediation

Upgrade electron to version 1.6.8 or higher.

References

medium severity

Denial of Service (DoS)

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@1.6.8.

Overview

electron is a framework for creating native applications with web technologies like JavaScript, HTML, and CSS. It takes care of the hard parts so you can focus on the core of your application.

Affected versions of the package are vulnerable to Denial of Service (DoS). When specifying webPreferences in the features parameter to the window.open function, it would throw an error in the main process and cause the service to crash.

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.

Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.

One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.

When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.

Two common types of DoS vulnerabilities:

  • High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.

  • Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package

Remediation

Upgrade electron to version 1.6.8 or higher.

References

medium severity

Improper Input Validation

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@12.2.1.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Improper Input Validation. It is possible to kill a renderer if it provides an unexpected FrameOwnerElementType.

Remediation

Upgrade electron to version 13.5.1, 12.2.1 or higher.

References

medium severity

Information Exposure

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@9.4.0.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Information Exposure. IPC messages sent from the main process to a subframe in the renderer process, through webContents.sendToFrame, event.reply or when using the remote module, can in some cases be delivered to the wrong frame.

Remediation

Upgrade electron to version 9.4.0, 10.2.0, 11.1.0, 12.0.0-beta.9 or higher.

References

medium severity

Information Exposure

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@10.4.1.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Information Exposure. The is a side-channel information leakage in autofill.

Remediation

Upgrade electron to version 11.4.0, 10.4.1 or higher.

References

medium severity

Out-of-Bounds

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@12.1.2.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Out-of-Bounds. An out of bounds write issue exists in engine.

Remediation

Upgrade electron to version 13.5.0, 12.1.2 or higher.

References

medium severity

Content Injection due to quoteless attributes

  • Vulnerable module: mustache
  • Introduced through: mustache@0.7.3

Detailed paths

  • Introduced through: vanguard-core@0.1.27 mustache@0.7.3
    Remediation: Upgrade to mustache@2.2.1.

Overview

When using attributes without quotes in a mustache template, an attacker can manipulate the input to introduce additional attributes, potentially executing code. This may lead to a Cross-site Scripting (XSS) vulnerability, assuming an attacker can influence the value entered into the template. If the mustache template is used to render user-generated content, this vulnerability may escalate to a persistent XSS vulnerability.

Example

For example, assume mustache was used to display user comments, using the following template: <a href={{email}}>{{name}}</a><pre>{{comment}}</pre>

If an attacker spoofed his email address and provided the following value: jane@evil.org onload=alert(document.cookie)

The resulting HTML would be: <a href=wizard@evil.org onload=alert(document.cookie)>Evil Wizard</a><pre>Busted!</pre>

References

medium severity

Root Path Disclosure

  • Vulnerable module: send
  • Introduced through: express@3.4.8

Detailed paths

  • Introduced through: vanguard-core@0.1.27 express@3.4.8 send@0.1.4
    Remediation: Upgrade to express@3.19.1.
  • Introduced through: vanguard-core@0.1.27 express@3.4.8 connect@2.12.0 send@0.1.4
    Remediation: Upgrade to express@4.0.0.

Overview

Send is a library for streaming files from the file system as an http response. It supports partial responses (Ranges), conditional-GET negotiation, high test coverage, and granular events which may be leveraged to take appropriate actions in your application or framework.

Affected versions of this package are vulnerable to a Root Path Disclosure.

Remediation

Upgrade send to version 0.11.1 or higher. If a direct dependency update is not possible, use snyk wizard to patch this vulnerability.

References

medium severity

Use After Free

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@9.4.2.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Use After Free via the Blink component in chromium.

Remediation

Upgrade electron to version 9.4.2, 10.3.1, 11.2.2 or higher.

References

medium severity

Improper Input Validation

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@10.4.4.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Improper Input Validation due to insufficient data validation that exists in V8.

Remediation

Upgrade electron to version 10.4.4, 12.0.6 or higher.

References

medium severity

Exposure of Resource to Wrong Sphere

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@12.2.2.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Exposure of Resource to Wrong Sphere. Inappropriate implementation in Background Fetch API in Google Chrome prior to 94.0.4606.54 allowed a remote attacker to leak cross-origin data via a crafted HTML page.

Remediation

Upgrade electron to version 14.1.1, 13.5.2, 12.2.2 or higher.

References

medium severity

Improper Access Control

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@12.2.2.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Improper Access Control. Inappropriate implementation in Background Fetch API in Google Chrome prior to 94.0.4606.54 allowed a remote attacker who had compromised the renderer process to leak cross-origin data via a crafted HTML page.

Remediation

Upgrade electron to version 14.1.1, 13.5.2, 12.2.2 or higher.

References

medium severity

URL Spoofing

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@1.7.6.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to URL Spoofing. When opening PDFs in PDFium resulting loading arbitrary PDFs that a hacker can control.

Remediation

Upgrade electron to version 1.7.6 or higher.

References

medium severity

Directory Traversal

  • Vulnerable module: send
  • Introduced through: express@3.4.8

Detailed paths

  • Introduced through: vanguard-core@0.1.27 express@3.4.8 send@0.1.4
    Remediation: Upgrade to express@3.16.10.
  • Introduced through: vanguard-core@0.1.27 express@3.4.8 connect@2.12.0 send@0.1.4
    Remediation: Upgrade to express@4.0.0.

Overview

send is a library for streaming files from the file system.

Affected versions of this package are vulnerable to Directory-Traversal attacks due to insecure comparison. When relying on the root option to restrict file access a malicious user may escape out of the restricted directory and access files in a similarly named directory. For example, a path like /my-secret is consedered fine for the root /my.

Details

A Directory Traversal attack (also known as path traversal) aims to access files and directories that are stored outside the intended folder. By manipulating files with "dot-dot-slash (../)" sequences and its variations, or by using absolute file paths, it may be possible to access arbitrary files and directories stored on file system, including application source code, configuration, and other critical system files.

Directory Traversal vulnerabilities can be generally divided into two types:

  • Information Disclosure: Allows the attacker to gain information about the folder structure or read the contents of sensitive files on the system.

st is a module for serving static files on web pages, and contains a vulnerability of this type. In our example, we will serve files from the public route.

If an attacker requests the following URL from our server, it will in turn leak the sensitive private key of the root user.

curl http://localhost:8080/public/%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/root/.ssh/id_rsa

Note %2e is the URL encoded version of . (dot).

  • Writing arbitrary files: Allows the attacker to create or replace existing files. This type of vulnerability is also known as Zip-Slip.

One way to achieve this is by using a malicious zip archive that holds path traversal filenames. When each filename in the zip archive gets concatenated to the target extraction folder, without validation, the final path ends up outside of the target folder. If an executable or a configuration file is overwritten with a file containing malicious code, the problem can turn into an arbitrary code execution issue quite easily.

The following is an example of a zip archive with one benign file and one malicious file. Extracting the malicious file will result in traversing out of the target folder, ending up in /root/.ssh/ overwriting the authorized_keys file:

2018-04-15 22:04:29 .....           19           19  good.txt
2018-04-15 22:04:42 .....           20           20  ../../../../../../root/.ssh/authorized_keys

Remediation

Upgrade to a version greater than or equal to 0.8.4.

References

low severity

Denial of Service (DoS)

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@1.6.8.

Overview

electron is a framework for creating native applications with web technologies like JavaScript, HTML, and CSS. It takes care of the hard parts so you can focus on the core of your application.

Affected versions of the package are vulnerable to Denial of Service (DoS). Certain built-in window APIs like alert, confirm, open, history.go, and postMessage would throw errors in the main process instead of the renderer processes when the arguments were invalid, causing the service to crash.

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.

Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.

One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.

When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.

Two common types of DoS vulnerabilities:

  • High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.

  • Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package

Remediation

Upgrade electron to version 1.6.8 or higher.

References

low severity

Out Of Bounds Read

  • Vulnerable module: electron
  • Introduced through: electron@0.4.1

Detailed paths

  • Introduced through: vanguard-core@0.1.27 electron@0.4.1
    Remediation: Upgrade to electron@10.4.4.

Overview

electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.

Affected versions of this package are vulnerable to Out Of Bounds Read. Blit11 would clip the destination rectangle with the destination size but ignore the result. gl::ClipRectangle returns false when the rectangles do not intersect at all, indicating the blit can be skipped.

Remediation

Upgrade electron to version 10.4.4, 11.4.4, 12.0.6 or higher.

References

low severity

Regular Expression Denial of Service (ReDoS)

  • Vulnerable module: mime
  • Introduced through: express@3.4.8

Detailed paths

  • Introduced through: vanguard-core@0.1.27 express@3.4.8 send@0.1.4 mime@1.2.11
    Remediation: Upgrade to express@4.16.0.
  • Introduced through: vanguard-core@0.1.27 express@3.4.8 connect@2.12.0 send@0.1.4 mime@1.2.11
    Remediation: Upgrade to express@4.0.0.

Overview

mime is a comprehensive, compact MIME type module.

Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS). It uses regex the following regex /.*[\.\/\\]/ in its lookup, which can cause a slowdown of 2 seconds for 50k characters.

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.

The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.

Let’s take the following regular expression as an example:

regex = /A(B|C+)+D/

This regular expression accomplishes the following:

  • A The string must start with the letter 'A'
  • (B|C+)+ The string must then follow the letter A with either the letter 'B' or some number of occurrences of the letter 'C' (the + matches one or more times). The + at the end of this section states that we can look for one or more matches of this section.
  • D Finally, we ensure this section of the string ends with a 'D'

The expression would match inputs such as ABBD, ABCCCCD, ABCBCCCD and ACCCCCD

It most cases, it doesn't take very long for a regex engine to find a match:

$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
0.04s user 0.01s system 95% cpu 0.052 total

$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
1.79s user 0.02s system 99% cpu 1.812 total

The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.

Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.

Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:

  1. CCC
  2. CC+C
  3. C+CC
  4. C+C+C.

The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.

From there, the number of steps the engine must use to validate a string just continues to grow.

String Number of C's Number of steps
ACCCX 3 38
ACCCCX 4 71
ACCCCCX 5 136
ACCCCCCCCCCCCCCX 14 65,553

By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.

Remediation

Upgrade mime to version 1.4.1, 2.0.3 or higher.

References

low severity

Regular Expression Denial of Service (ReDoS)

  • Vulnerable module: tar
  • Introduced through: connect-sqlite3@0.9.13

Detailed paths

  • Introduced through: vanguard-core@0.1.27 connect-sqlite3@0.9.13 sqlite3@5.0.2 node-gyp@3.8.0 tar@2.2.2

Overview

tar is a full-featured Tar for Node.js.

Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS). When stripping the trailing slash from files arguments, the f.replace(/\/+$/, '') performance of this function can exponentially degrade when f contains many / characters resulting in ReDoS.

This vulnerability is not likely to be exploitable as it requires that the untrusted input is being passed into the tar.extract() or tar.list() array of entries to parse/extract, which would be unusual.

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.

The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.

Let’s take the following regular expression as an example:

regex = /A(B|C+)+D/

This regular expression accomplishes the following:

  • A The string must start with the letter 'A'
  • (B|C+)+ The string must then follow the letter A with either the letter 'B' or some number of occurrences of the letter 'C' (the + matches one or more times). The + at the end of this section states that we can look for one or more matches of this section.
  • D Finally, we ensure this section of the string ends with a 'D'

The expression would match inputs such as ABBD, ABCCCCD, ABCBCCCD and ACCCCCD

It most cases, it doesn't take very long for a regex engine to find a match:

$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
0.04s user 0.01s system 95% cpu 0.052 total

$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
1.79s user 0.02s system 99% cpu 1.812 total

The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.

Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.

Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:

  1. CCC
  2. CC+C
  3. C+CC
  4. C+C+C.

The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.

From there, the number of steps the engine must use to validate a string just continues to grow.

String Number of C's Number of steps
ACCCX 3 38
ACCCCX 4 71
ACCCCCX 5 136
ACCCCCCCCCCCCCCX 14 65,553

By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.

Remediation

Upgrade tar to version 6.1.4, 5.0.8, 4.4.16 or higher.

References