Lookup for vulnerable packages by Package URL.
| Purl | pkg:npm/electron@4.0.8 |
| Type | npm |
| Namespace | |
| Name | electron |
| Version | 4.0.8 |
| Qualifiers |
|
| Subpath | |
| Is_vulnerable | true |
| Next_non_vulnerable_version | 9.4.0 |
| Latest_non_vulnerable_version | 42.0.0-alpha.5 |
| Affected_by_vulnerabilities |
| 0 |
| url |
VCID-c9ut-fk1h-gfe4 |
| vulnerability_id |
VCID-c9ut-fk1h-gfe4 |
| summary |
Trust Boundary Violation
In Electron, 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. |
| references |
|
| fixed_packages |
|
| aliases |
CVE-2020-15096, GHSA-6vrv-94jv-crrg
|
| risk_score |
3.0 |
| exploitability |
0.5 |
| weighted_severity |
6.1 |
| resource_url |
http://public2.vulnerablecode.io/vulnerabilities/VCID-c9ut-fk1h-gfe4 |
|
| 1 |
| url |
VCID-p3vt-avbt-kyed |
| vulnerability_id |
VCID-p3vt-avbt-kyed |
| summary |
IPC messages delivered to the wrong frame in Electron
IPC messages sent from the main process to a subframe in the renderer process, through `webContents.sendToFrame`, `event.reply` or when using the `remote` module, can in some cases be delivered to the wrong frame.
If your app does ANY of the following, then it is impacted by this issue:
- Uses `remote`
- Calls `webContents.sendToFrame`
- Calls `event.reply` in an IPC message handler |
| references |
| 0 |
|
| 1 |
|
| 2 |
|
| 3 |
|
| 4 |
|
| 5 |
|
| 6 |
|
| 7 |
|
| 8 |
|
| 9 |
|
| 10 |
|
| 11 |
|
| 12 |
|
|
| fixed_packages |
|
| aliases |
CVE-2020-26272, GHSA-hvf8-h2qh-37m9
|
| risk_score |
3.1 |
| exploitability |
0.5 |
| weighted_severity |
6.2 |
| resource_url |
http://public2.vulnerablecode.io/vulnerabilities/VCID-p3vt-avbt-kyed |
|
|
| Fixing_vulnerabilities |
|
| Risk_score | null |
| Resource_url | http://public2.vulnerablecode.io/packages/pkg:npm/electron@4.0.8 |