GHSA-hvf8-h2qh-37m9 CVE-2020-26272
IPC messages delivered to the wrong frame in Electron
- Severity
- 5.4 / 10
- Medium · CVSS 3.1
- Exploit chance (EPSS)
- 1.75%
- Chance of exploitation in the next 30 days. Higher than 77.81% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-668 Exposure of Resource to Wrong Sphere
- Fix
9.4.0- Upgrade electron to this version or later
Description
Impact
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.replyin an IPC message handler
Patches
This has been fixed in the following versions:
- 9.4.0
- 10.2.0
- 11.1.0
- 12.0.0-beta.9
Workarounds
There are no workarounds for this issue.
For more information
If you have any questions or comments about this advisory, email us at security@electronjs.org.
Affected versions
npm
| Package | Vulnerable | Fixed in |
|---|---|---|
| electron | < 9.4.0 |
9.4.0 |
| electron | >= 10.0.0, < 10.2.0 |
10.2.0 |
| electron | >= 11.0.0, < 11.1.0 |
11.1.0 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
electron npm → 9.4.0
- npm
npm install electron@9.4.0- yarn
yarn add electron@9.4.0- pnpm
pnpm add electron@9.4.0
Severity breakdown
CVSS 3.1 5.4
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
Weakness
CWE-668: Exposure of Resource to Wrong Sphere
The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource.
References
Advisories
Other links
- github.com/electron/electron/security/advisories/GHSA-hvf8-h2qh-37m9
- github.com/electron/electron/pull/26875
- github.com/electron/electron/commit/07a1c2a3e5845901f7e2eda9506695be58edc73c
- github.com/electron/electron/commit/0bbd268eb4caf35604443df5ff196980dd49e208
- github.com/electron/electron/commit/36c695ce2a7e22c07fe1e30c61c00d20371daee2
- github.com/electron/electron/commit/429400040ecb16a21d19936658579e65a797e4cc
- github.com/electron/electron/commit/5c8e7e8b7f485ceafa8b271086d7b87e1de9dedd
- github.com/electron/electron/releases/tag/v9.4.0
- electronjs.org/releases/stable
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-qqvq-6xgj-jw8g Electron affected by libvpx's heap buffer overflow in vp8 encoding | High Known exploited | Also affects electron |
| GHSA-j7hp-h8jx-5ppr libwebp: OOB write in BuildHuffmanTable | High Known exploited | Also affects electron |
| GHSA-995f-9x5r-2rcj Heap buffer overflow in GPU | Critical Known exploited | Also affects electron |
| GHSA-jr5w-w6x2-84p9 Electron: Mitigation for compromised eMudhra intermediate certificates | High | Also affects electron |
| GHSA-h3v5-h239-pg29 Electron: Off-screen rendering on macOS trusts GPU-supplied frame geometry | Low | Also affects electron |
| GHSA-3qxv-5xgr-q7w9 Electron: Frame subscription trusts GPU-supplied frame geometry | Low | Also affects electron |
| GHSA-997q-gvvc-jwmx Electron: openExternal permission requests can be attributed to the wrong origin | Medium | Also affects electron |
| GHSA-fw47-9c62-h3vw Electron: HID and USB permission checks can be attributed to the wrong origin | Medium | Also affects electron |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor