Electron 8.5.2/9.3.1/10.1.2/11.0.0 Context Isolation sandbox
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in Electron 8.5.2/9.3.1/10.1.2/11.0.0. This issue affects some unknown processing of the component Context Isolation. This manipulation causes sandbox. This vulnerability is handled as CVE-2020-15215. There is not any exploit available.
Details
A vulnerability was found in Electron 8.5.2/9.3.1/10.1.2/11.0.0. It has been declared as critical. Affected by this vulnerability is an unknown functionality of the component Context Isolation. The manipulation with an unknown input leads to a sandbox vulnerability. The CWE definition for the vulnerability is CWE-265. As an impact it is known to affect confidentiality, integrity, and availability.
The weakness was released 10/07/2020. It is possible to read the advisory at github.com. This vulnerability is known as CVE-2020-15215. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1611 according to MITRE ATT&CK.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.5
VulDB Base Score: 5.5
VulDB Temp Score: 5.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: SandboxCWE: CWE-265 / CWE-264
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
06/25/2020 🔍10/07/2020 🔍
10/07/2020 🔍
11/17/2020 🔍
Sources
Product: github.comAdvisory: github.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2020-15215 (🔍)
GCVE (CVE): GCVE-0-2020-15215
GCVE (VulDB): GCVE-100-162331
Entry
Created: 10/07/2020 10:45Updated: 11/17/2020 00:11
Changes: 10/07/2020 10:45 (11), 10/07/2020 10:48 (24), 11/15/2020 10:22 (1), 11/17/2020 00:06 (3), 11/17/2020 00:11 (7)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.