Electron: HTTP Response Header Injection in custom protocol handlers and webRequest
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 38.8.6, 39.8.3, 40.8.3, and 41.0.3, apps that register custom protocol handlers via protocol.handle() / protocol.registerSchemesAsPrivileged() or modify response headers via webRequest.onHeadersReceived may be vulnerable to HTTP response header injection if attacker-controlled input is reflected into a response header name or value. An attacker who can influence a header value may be able to inject additional response headers, affecting cookies, content security policy, or cross-origin access controls. Apps that do not reflect external input into response headers are not affected. This issue has been patched in versions 38.8.6, 39.8.3, 40.8.3, and 41.0.3.
From the CVE record · GitHub_M
Electron apps that use custom protocol handlers or modify response headers may be vulnerable if they reflect attacker-controlled input into a response header name or value. An attacker who can influence a header value may inject additional response headers, affecting cookies, content security policy, or cross-origin access controls. Apps that do not reflect external input into response headers are not affected; the input does not specify whether authentication or user interaction is required.
Teams running npm electron versions below 38.8.6, from 39.0.0-alpha.1 to below 39.8.3, from 40.0.0-alpha.1 to below 40.8.3, or from 41.0.0-alpha.1 to below 41.0.3 should check their apps.