GitHub Electron 1.7.15/1.8.7/2.0.7/3.0.0-beta.6 WebPreferences iFRAME Element 7pk security

Summaryinfo

A vulnerability was found in GitHub Electron 1.7.15/1.8.7/2.0.7/3.0.0-beta.6. It has been rated as critical. This impacts an unknown function of the component WebPreferences. Performing a manipulation as part of iFRAME Element results in 7pk security. This vulnerability is known as CVE-2018-15685. Remote exploitation of the attack is possible. Furthermore, an exploit is available.

Detailsinfo

A vulnerability classified as critical has been found in GitHub Electron 1.7.15/1.8.7/2.0.7/3.0.0-beta.6 (Bug Tracking Software). This affects an unknown function of the component WebPreferences. The manipulation as part of a iFRAME Element leads to a 7pk security vulnerability. CWE is classifying the issue as CWE-254. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

GitHub Electron 1.7.15, 1.8.7, 2.0.7, and 3.0.0-beta.6, in certain scenarios involving IFRAME elements and "nativeWindowOpen: true" or "sandbox: true" options, is affected by a WebPreferences vulnerability that can be leveraged to perform remote code execution.

The bug was discovered 08/22/2018. The weakness was published 08/23/2018 (Website). The advisory is shared at electronjs.org. This vulnerability is uniquely identified as CVE-2018-15685 since 08/21/2018. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are unknown but a public exploit is available. MITRE ATT&CK project uses the attack technique T1211 for this issue.

The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $0-$5k. The commercial vulnerability scanner Qualys is able to test this issue with plugin 371158 (Node.js Electron Module WebPreferences Remote Code Execution Vulnerability).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at Exploit-DB (45272). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Bug Tracking Software

Vendor

• GitHub

Name

• Electron

Version

• 1.7.15
• 1.8.7
• 2.0.7
• 3.0.0-beta.6

License

• open-source

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion