CVE-2022-29247

Workarounds

Ensure that all IPC message handlers appropriately validate senderFrame as per our security tutorial here.

For more information

If you have any questions or comments about this advisory, email us at [email protected].

This vulnerability allows a renderer with JS execution to obtain access to a new renderer process with nodeIntegrationInSubFrames enabled which in turn allows effective access to ipcRenderer.

Please note the misleadingly named nodeIntegrationInSubFrames option does not implicitly grant Node.js access rather it depends on the existing sandbox setting. If your application is sandboxed then nodeIntegrationInSubFrames just gives access to the sandboxed renderer APIs (which includes ipcRenderer).

If your application then additionally exposes IPC messages without IPC senderFrame validation that perform privileged actions or return confidential data this access to ipcRenderer can in turn compromise your application / user even with the sandbox enabled.

CVE-2022-29247 has a CVSS score of 2.2 (Low). The vector is network-reachable, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (15.5.5, 16.2.6, 17.2.0, 18.0.0-beta.6); upgrading removes the vulnerable code path.

Kodem intelligence

This has been patched and the following Electron versions contain the fix:

• 18.0.0-beta.6
• 17.2.0
• 16.2.6
• 15.5.5

1. What is CVE-2022-29247? CVE-2022-29247 is a low-severity security vulnerability in electron (npm), affecting versions < 15.5.5. It is fixed in 15.5.5, 16.2.6, 17.2.0, 18.0.0-beta.6.
2. How severe is CVE-2022-29247? CVE-2022-29247 has a CVSS score of 2.2 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of electron are affected by CVE-2022-29247? electron (npm) versions < 15.5.5 is affected.
4. Is there a fix for CVE-2022-29247? Yes. CVE-2022-29247 is fixed in 15.5.5, 16.2.6, 17.2.0, 18.0.0-beta.6. Upgrade to this version or later.
5. Is CVE-2022-29247 exploitable, and should I be worried? Whether CVE-2022-29247 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2022-29247 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2022-29247?
   • Upgrade electron to 15.5.5 or later
   • Upgrade electron to 16.2.6 or later
   • Upgrade electron to 17.2.0 or later
   • Upgrade electron to 18.0.0-beta.6 or later

Other vulnerabilities in electron