Approved changes feed: RSS · Atom

cpe:2.3:a:electronjs:electron:24.0.0:beta5:*:*:*:node.js:*:*

part: a version: 24.0.0 update: beta5

VendorElectronjs (2af93ff4-38f6-5aef-acc5-80ca92aa0b83)
ProductElectron (3ffe6bdf-afda-502c-ac98-8ec4a42261cc)
Edition*
Language*
Software edition*
Target softwarenode.js
Target hardware*
Other*
NotesImported from NVD CPE 2.0 feed

PURL mappings

PURLSourceLast updated
pkg:github/electron/electron purl2cpe 2026-06-01 10:17:08.317705
pkg:gitlab/immersaview/electron purl2cpe 2026-06-01 10:17:08.317706
pkg:npm/electron purl2cpe 2026-06-01 10:17:08.317707
pkg:sourceforge/electron.mirror purl2cpe 2026-06-01 10:17:08.317709

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2023-29198 vulnerable 2026-06-08 06:02:39.115662 Context isolation bypass via nested unserializable return value in Electron
MEDIUM (6)
Electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS. Electron apps using `contextIsolation` and `contextBridge` are affected. This 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. This issue is only exploitable if an API exposed to the main world via `contextBridge` can return an object or array that contains a javascript object which cannot be serialized, for instance, a canvas rendering context. This would normally result in an exception being thrown `Error: object could not be cloned`. The app side workaround is to ensure that such a case is not possible. Ensure all values returned from a function exposed over the context bridge are supported. This issue has been fixed in versions `25.0.0-alpha.2`, `24.0.1`, `23.2.3`, and `22.3.6`.
Published: 2023-09-06T20:13:56.313Z
Updated: 2024-09-26T15:12:58.704Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.