CVE-2020-262725.4MediumCWE-668

CVE-2020-26272: Electron vulnerable to ID collision when routing IPC messages to renderers containing OOPIFs

electron

Affected: electron · Exploitation: possible (1 to 10%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

1.8%probability of exploitation in the next 30 days

78th percentile

050100

Higher than 78% of scored CVEs

5.4MediumCVSS 3.1

LowMediumHighCrit.

DescriptionCVE.org

The Electron framework lets users write cross-platform desktop applications using JavaScript, HTML and CSS. In versions of Electron IPC prior to 9.4.0, 10.2.0, 11.1.0, and 12.0.0-beta.9, 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 uses remote, calls webContents.sendToFrame, or calls event.reply in an IPC message handler then it is impacted by this issue. This has been fixed in versions 9.4.0, 10.2.0, 11.1.0, and 12.0.0-beta.9. There are no known workarounds for this issue.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

electron · electron< 9.4.0; >= 10.0.0, < 10.2.0; >= 11.0.0, < 11.1.0

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Possible (1 to 10%). EPSS between 1% and 10%.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Exposure of Resource to Wrong Sphere · Access Control
Vendor: electron
Published: January 2021
Band: Possible (1 to 10%), January 2021

CoverageNo articles yet

No CyberSIXT article names CVE-2020-26272 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.