Electron SameSite cookie exposure in link-opened windows
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 versions 42.11.3, 43.7.0, 44.3.0, and 45.0.0-alpha.6, Electron treated pages opened into a new window from links as application-initiated navigations instead of preserving the page containing the link as the initiator. The resulting top-level request could be classified as same-site, causing SameSite=Strict cookies to be sent and Sec-Fetch-Site not to identify the initiating page. An application that loads untrusted content and permits it to open new windows could therefore allow that content to make a credentialed request to another site that relies on SameSite cookies for CSRF protection. This issue is fixed in versions 42.11.3, 43.7.0, 44.3.0, and 45.0.0-alpha.6.
From the CVE record · GitHub_M
Electron can misclassify a new-window navigation from a link as application-initiated, causing SameSite=Strict cookies to be sent and obscuring the initiating page in Sec-Fetch-Site. If an application loads untrusted content and lets it open new windows, that content can make a credentialed request to another site that relies on SameSite cookies for CSRF protection.
Engineers running applications with the npm electron package should check versions earlier than 42.11.3, 43.0.0-alpha.1 through 43.6.x, 44.0.0-alpha.1 through versions before 44.3.0, and 45.0.0-alpha.1 through versions before 45.0.0-alpha.6.