You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
CVE-2023-29198 - High Severity Vulnerability
Build cross platform desktop apps with JavaScript, HTML, and CSS
Library home page: https://registry.npmjs.org/electron/-/electron-16.0.8.tgz
Dependency Hierarchy:
Found in HEAD commit: 16df54b5db88f4c8b21295a7ded5e65ec8446eaa
Found in base branch: main
Electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS. Electron apps using
contextIsolation
andcontextBridge
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 viacontextBridge
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 thrownError: 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 versions25.0.0-alpha.2
,24.0.1
,23.2.3
, and22.3.6
.Publish Date: 2023-09-06
URL: CVE-2023-29198
Base Score Metrics:
Type: Upgrade version
Origin: https://www.cve.org/CVERecord?id=CVE-2023-29198
Release Date: 2023-09-06
Fix Resolution: 22.3.6
Step up your Open Source Security Game with Mend here
The text was updated successfully, but these errors were encountered: