Electron up to 7.2.3/8.2.3/9.0.0-beta20 Isolation trust boundary violation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Electron up to 7.2.3/8.2.3/9.0.0-beta20. It has been rated as critical. This issue affects some unknown processing of the component Isolation Handler. Performing a manipulation results in trust boundary violation. This vulnerability is cataloged as CVE-2020-4077. It is possible to initiate the attack remotely. There is no exploit available. Upgrading the affected component is advised.
Details
A vulnerability classified as critical has been found in Electron up to 7.2.3/8.2.3/9.0.0-beta20. This affects an unknown function of the component Isolation Handler. The manipulation with an unknown input leads to a trust boundary violation vulnerability. CWE is classifying the issue as CWE-501. The product mixes trusted and untrusted data in the same data structure or structured message. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
In Electron before versions 7.2.4, 8.2.4, and 9.0.0-beta21, there is a context isolation bypass. Code running in the main world context in the renderer can reach into the isolated Electron context and perform privileged actions. Apps using both `contextIsolation` and `contextBridge` are affected. This is fixed in versions 9.0.0-beta.21, 8.2.4 and 7.2.4.
The weakness was shared 07/07/2020 (GitHub Repository). The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2020-4077 since 12/30/2019. It is possible to initiate the attack remotely. The successful exploitation requires a authentication. Neither technical details nor an exploit are publicly available.
Upgrading to version 7.2.4, 8.2.4 or 9.0.0-beta21 eliminates this vulnerability.
The entries VDB-157688 and VDB-157687 are related to this item. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.1
VulDB Base Score: 7.4
VulDB Temp Score: 6.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.7
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Trust boundary violationCWE: CWE-501
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Electron 7.2.4/8.2.4/9.0.0-beta21
Timeline
12/30/2019 🔍07/07/2020 🔍
07/07/2020 🔍
10/28/2020 🔍
Sources
Product: github.comAdvisory: github.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2020-4077 (🔍)
GCVE (CVE): GCVE-0-2020-4077
GCVE (VulDB): GCVE-100-157689
See also: 🔍
Entry
Created: 07/07/2020 09:51Updated: 10/28/2020 22:15
Changes: 07/07/2020 09:51 (39), 07/07/2020 09:56 (11), 10/28/2020 22:06 (1), 10/28/2020 22:15 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.