Electron: ProtocolResponse.url reuses the default session cache instead of the registering session
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 40.10.6, 41.9.1, 42.5.1, 43.0.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- electron electron
From 40.0.0-alpha.1 · fixed in 40.10.6; From 41.0.0-alpha.1 · fixed in 41.9.1; From 42.0.0-alpha.1 · fixed in 42.5.1; From 43.0.0-alpha.1 · fixed in 43.0.0
- electronnpm
From 43.0.0-alpha.1 · fixed in 43.0.0
- electronnpm
From 42.0.0-alpha.1 · fixed in 42.5.1
- electronnpm
From 41.0.0-alpha.1 · fixed in 41.9.1
- electronnpm
From 40.0.0-alpha.1 · fixed in 40.10.6