ID CVE-2020-4075
Summary In Electron before versions 7.2.4, 8.2.4, and 9.0.0-beta21, arbitrary local file read is possible by defining unsafe window options on a child window opened via window.open. As a workaround, ensure you are calling `event.preventDefault()` on all new-window events where the `url` or `options` is not something you expect. This is fixed in versions 9.0.0-beta.21, 8.2.4 and 7.2.4.
References
Vulnerable Configurations
  • cpe:2.3:a:electronjs:electron:7.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:electronjs:electron:7.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:electronjs:electron:8.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:electronjs:electron:8.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:electronjs:electron:9.0.0:-:*:*:*:*:*:*
    cpe:2.3:a:electronjs:electron:9.0.0:-:*:*:*:*:*:*
  • cpe:2.3:a:electronjs:electron:9.0.0:beta1:*:*:*:*:*:*
    cpe:2.3:a:electronjs:electron:9.0.0:beta1:*:*:*:*:*:*
  • cpe:2.3:a:electronjs:electron:9.0.0:beta10:*:*:*:*:*:*
    cpe:2.3:a:electronjs:electron:9.0.0:beta10:*:*:*:*:*:*
  • cpe:2.3:a:electronjs:electron:9.0.0:beta11:*:*:*:*:*:*
    cpe:2.3:a:electronjs:electron:9.0.0:beta11:*:*:*:*:*:*
  • cpe:2.3:a:electronjs:electron:9.0.0:beta12:*:*:*:*:*:*
    cpe:2.3:a:electronjs:electron:9.0.0:beta12:*:*:*:*:*:*
  • cpe:2.3:a:electronjs:electron:9.0.0:beta13:*:*:*:*:*:*
    cpe:2.3:a:electronjs:electron:9.0.0:beta13:*:*:*:*:*:*
  • cpe:2.3:a:electronjs:electron:9.0.0:beta14:*:*:*:*:*:*
    cpe:2.3:a:electronjs:electron:9.0.0:beta14:*:*:*:*:*:*
  • cpe:2.3:a:electronjs:electron:9.0.0:beta15:*:*:*:*:*:*
    cpe:2.3:a:electronjs:electron:9.0.0:beta15:*:*:*:*:*:*
  • cpe:2.3:a:electronjs:electron:9.0.0:beta16:*:*:*:*:*:*
    cpe:2.3:a:electronjs:electron:9.0.0:beta16:*:*:*:*:*:*
  • cpe:2.3:a:electronjs:electron:9.0.0:beta17:*:*:*:*:*:*
    cpe:2.3:a:electronjs:electron:9.0.0:beta17:*:*:*:*:*:*
  • cpe:2.3:a:electronjs:electron:9.0.0:beta18:*:*:*:*:*:*
    cpe:2.3:a:electronjs:electron:9.0.0:beta18:*:*:*:*:*:*
  • cpe:2.3:a:electronjs:electron:9.0.0:beta19:*:*:*:*:*:*
    cpe:2.3:a:electronjs:electron:9.0.0:beta19:*:*:*:*:*:*
  • cpe:2.3:a:electronjs:electron:9.0.0:beta2:*:*:*:*:*:*
    cpe:2.3:a:electronjs:electron:9.0.0:beta2:*:*:*:*:*:*
  • cpe:2.3:a:electronjs:electron:9.0.0:beta20:*:*:*:*:*:*
    cpe:2.3:a:electronjs:electron:9.0.0:beta20:*:*:*:*:*:*
  • cpe:2.3:a:electronjs:electron:9.0.0:beta3:*:*:*:*:*:*
    cpe:2.3:a:electronjs:electron:9.0.0:beta3:*:*:*:*:*:*
  • cpe:2.3:a:electronjs:electron:9.0.0:beta4:*:*:*:*:*:*
    cpe:2.3:a:electronjs:electron:9.0.0:beta4:*:*:*:*:*:*
  • cpe:2.3:a:electronjs:electron:9.0.0:beta5:*:*:*:*:*:*
    cpe:2.3:a:electronjs:electron:9.0.0:beta5:*:*:*:*:*:*
  • cpe:2.3:a:electronjs:electron:9.0.0:beta6:*:*:*:*:*:*
    cpe:2.3:a:electronjs:electron:9.0.0:beta6:*:*:*:*:*:*
  • cpe:2.3:a:electronjs:electron:9.0.0:beta7:*:*:*:*:*:*
    cpe:2.3:a:electronjs:electron:9.0.0:beta7:*:*:*:*:*:*
  • cpe:2.3:a:electronjs:electron:9.0.0:beta8:*:*:*:*:*:*
    cpe:2.3:a:electronjs:electron:9.0.0:beta8:*:*:*:*:*:*
  • cpe:2.3:a:electronjs:electron:9.0.0:beta9:*:*:*:*:*:*
    cpe:2.3:a:electronjs:electron:9.0.0:beta9:*:*:*:*:*:*
CVSS
Base: 2.1 (as of 13-07-2020 - 18:51)
Impact:
Exploitability:
CWE CWE-552
CAPEC
  • Kerberoasting
    Through the exploitation of how service accounts leverage Kerberos authentication with Service Principal Names (SPNs), the adversary obtains and subsequently cracks the hashed credentials of a service account target to exploit its privileges. The Kerberos authentication protocol centers around a ticketing system which is used to request/grant access to services and to then access the requested services. As an authenticated user, the adversary may request Active Directory and obtain a service ticket with portions encrypted via RC4 with the private key of the authenticated account. By extracting the local ticket and saving it disk, the adversary can brute force the hashed value to reveal the target account credentials.
  • Probe System Files
    An adversary obtains unauthorized information due to improperly protected files. If an application stores sensitive information in a file that is not protected by proper access control, then an adversary can access the file and search for sensitive information.
  • Collect Data from Common Resource Locations
    An adversary exploits well-known locations for resources for the purposes of undermining the security of the target. In many, if not most systems, files and resources are organized in a default tree structure. This can be useful for adversaries because they often know where to look for resources or files that are necessary for attacks. Even when the precise location of a targeted resource may not be known, naming conventions may indicate a small area of the target machine's file tree where the resources are typically located. For example, configuration files are normally stored in the /etc director on Unix systems. Adversaries can take advantage of this to commit other types of attacks.
Access
VectorComplexityAuthentication
LOCAL LOW NONE
Impact
ConfidentialityIntegrityAvailability
PARTIAL NONE NONE
cvss-vector via4 AV:L/AC:L/Au:N/C:P/I:N/A:N
refmap via4
confirm https://github.com/electron/electron/security/advisories/GHSA-f9mq-jph6-9mhm
misc https://www.electronjs.org/releases/stable?page=3#release-notes-for-v824
Last major update 13-07-2020 - 18:51
Published 07-07-2020 - 00:15
Last modified 13-07-2020 - 18:51
Back to Top