Electron: ProtocolResponse.url reuses the default session cache instead of the registering session
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 40.10.6, 41.9.1, 42.5.1, and 43.0.0, when a custom protocol handler returned a ProtocolResponse with a url and no session, Electron made the upstream request through defaultSession instead of the session that handled the protocol. A cached response could then be reused across otherwise isolated session partitions. Apps that use ProtocolResponse.url, omit ProtocolResponse.session, and rely on separate sessions to isolate content are affected. This issue is fixed in versions 40.10.6, 41.9.1, 42.5.1, and 43.0.0.
From the CVE record · GitHub_M
When a custom protocol handler returns a ProtocolResponse with a url but no session, Electron makes the upstream request through defaultSession instead of the session handling the protocol. A cached response can then be reused across otherwise isolated session partitions in apps that rely on those partitions to isolate content.
Check apps using npm electron versions >=40.0.0-alpha.1 <40.10.6, >=41.0.0-alpha.1 <41.9.1, >=42.0.0-alpha.1 <42.5.1, or >=43.0.0-alpha.1 <43.0.0, particularly those using ProtocolResponse.url without ProtocolResponse.session.