Electron up to 6.1.0/7.2.3/8.2.3/9.0.0-beta20 Context Isolation trust boundary violation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.9 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as critical has been discovered in Electron up to 6.1.0/7.2.3/8.2.3/9.0.0-beta20. This affects an unknown part of the component Context Isolation. Such manipulation leads to trust boundary violation. This vulnerability is documented as CVE-2020-15096. The attack can be executed remotely. There is not any exploit available. It is advisable to upgrade the affected component.
Details
A vulnerability was found in Electron up to 6.1.0/7.2.3/8.2.3/9.0.0-beta20 and classified as critical. Affected by this issue is an unknown functionality of the component Context Isolation. The manipulation with an unknown input leads to a trust boundary violation vulnerability. Using CWE to declare the problem leads to CWE-501. The product mixes trusted and untrusted data in the same data structure or structured message. Impacted is confidentiality, integrity, and availability. CVE summarizes:
In Electron before versions 6.1.1, 7.2.4, 8.2.4, and 9.0.0-beta21, there 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. Apps using "contextIsolation" are affected. There are no app-side workarounds, you must update your Electron version to be protected. This is fixed in versions 6.1.1, 7.2.4, 8.2.4, and 9.0.0-beta21.
The weakness was released 07/07/2020 (GitHub Repository). The advisory is shared for download at github.com. This vulnerability is handled as CVE-2020-15096 since 06/25/2020. The attack may be launched remotely. The exploitation needs additional levels of successful authentication. There are neither technical details nor an exploit publicly available.
Upgrading to version 6.1.1, 7.2.4, 8.2.4 or 9.0.0-beta21 eliminates this vulnerability.
Once again VulDB remains the best source for vulnerability data.
Product
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.7VulDB Meta Temp Score: 6.3
VulDB Base Score: 6.6
VulDB Temp Score: 5.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.8
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 6.1.1/7.2.4/8.2.4/9.0.0-beta21
Timeline
06/25/2020 🔍07/07/2020 🔍
07/07/2020 🔍
10/28/2020 🔍
Sources
Product: github.comAdvisory: github.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2020-15096 (🔍)
GCVE (CVE): GCVE-0-2020-15096
GCVE (VulDB): GCVE-100-157676
Entry
Created: 07/07/2020 09:32Updated: 10/28/2020 21:30
Changes: 07/07/2020 09:32 (38), 07/07/2020 09:37 (11), 10/28/2020 21:23 (1), 10/28/2020 21:30 (1)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.