CVE-2022-29247
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedElectron is a framework for writing cross-platform desktop applications using JavaScript (JS), HTML, and CSS. A vulnerability in versions prior to 18.0.0-beta.6, 17.2.0, 16.2.6, and 15.5.5 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`. The `nodeIntegrationInSubFrames` option does not implicitly grant Node.js access. Rather, it depends on the existing sandbox setting. If an application is sandboxed, then `nodeIntegrationInSubFrames` just gives access to the sandboxed renderer APIs, which include `ipcRenderer`. If the 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. Electron versions 18.0.0-beta.6, 17.2.0, 16.2.6, and 15.5.5 contain a fix for this issue. As a workaround, ensure that all IPC message handlers appropriately validate `senderFrame`.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIn affected Electron versions prior to 18.0.0-beta.6, 17.2.0, 16.2.6, and 15.5.5, a renderer process with JavaScript execution can obtain access to a new renderer with nodeIntegrationInSubFrames enabled, which provides access to ipcRenderer even in sandboxed applications. If IPC handlers lack senderFrame validation, attackers can perform privileged actions or access confidential data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 15.5.5>= 16.0.1, < 16.2.6>= 17.0.1, < 17.2.0= 16.0.0= 17.0.0= 18.0.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Electron versionCheck package.json for the electron dependency version, or run 'electron --version' in the application environment, or inspect the electron binary directlyAffected if The version is less than 15.5.5, or between 16.0.0-16.2.5, or between 17.0.0-17.1.x, or exactly 18.0.0 (non-beta)
-
Locate webPreferences configurationSearch source code for BrowserWindow or webviewTag creation where webPreferences are defined, typically in main process files like main.js, main.ts, or index.jsAffected if nodeIntegrationInSubFrames is set to true or is not explicitly set to false
-
Verify senderFrame validation on IPC handlersSearch source code for ipcMain.on, ipcMain.handle, or ipcRenderer invocations. Inspect each IPC handler to confirm it validates event.senderFrame (or event.senderFrame.url, event.senderFrame.getURL()) before processing sensitive data or privileged actionsAffected if Any IPC handler processes privileged actions or accesses confidential data without checking event.senderFrame or event.senderFrame.url
-
Check if application uses webviewTagSearch for webviewTag in the application (in BrowserWindow webPreferences or in HTML/JS), as this feature combined with nodeIntegrationInSubFrames increases the attack surfaceAffected if webviewTag is enabled and nodeIntegrationInSubFrames is true or unset, and IPC handlers lack senderFrame validation
The environment is affected if running an Electron version in the vulnerable range AND nodeIntegrationInSubFrames is enabled or not explicitly disabled, AND at least one IPC handler that processes sensitive data lacks senderFrame validation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped15.5.516.2.617.2.0
Update Electron to version 18.0.0-beta.6, 17.2.0, 16.2.6, or 15.5.5 or higher; alternatively, implement senderFrame validation on all IPC message handlers to verify the sender's origin.
Electron 15.5.5, 16.2.6, 17.2.0, or 18.x stable (minimum 18.0.0-beta.6)
- Upgrade Electron to version 15.5.5, 16.2.6, 17.2.0, or a version >= 18.0.0 (stable release)
- After upgrading, rebuild and test your application to ensure functionality is intact
- If upgrading is not immediately possible, implement a config workaround by adding senderFrame validation to all IPC message handlers: check that event.senderFrame is valid and originates from an expected origin before performing privileged actions
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-29247 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-29247 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data