Electron: contextBridge object copy honors prototype setters
electron
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| electron npm |
|
|
electron
| Product | Affected | Fixed in |
|---|---|---|
| electron npm |
|
|
Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. Prior to 39.8.9, 40.9.2, 41.2.2, and 42.0.0-beta.4, objects copied across the contextBridge boundary from untrusted content could carry an attacker-influenced prototype, enabling prototype-pollution-style attacks against preload code despite context isolation being enabled. Apps are only affected if their preload code accepts object arguments from untrusted content and reads properties from them without own-property checks, while apps that only accept primitive arguments or validate object arguments are not affected. This issue is fixed in 39.8.9, 40.9.2, 41.2.2, and 42.0.0-beta.4.
From the CVE record · GitHub_M
Objects copied from untrusted content across Electron’s contextBridge boundary could carry an attacker-influenced prototype, enabling prototype-pollution-style attacks against preload code despite context isolation. An app is affected only if its preload code accepts object arguments from untrusted content and reads their properties without own-property checks.
Teams using the npm electron package should check versions below 39.8.9, 40.0.0-alpha.1 through versions below 40.9.2, 41.0.0-alpha.1 through versions below 41.2.2, and 42.0.0-alpha.1 through versions below 42.0.0-beta.4.