Electron: HTTP Response Header Injection in custom protocol handlers and webRequest
- 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 38.8.6, 39.8.3, 40.8.3, 41.0.3
- 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 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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- electron electron
fixed in 38.8.6; From 39.0.0-alpha.1 · fixed in 39.8.3; From 40.0.0-alpha.1 · fixed in 40.8.3; From 41.0.0-alpha.1 · fixed in 41.0.3
- electronnpm
fixed in 38.8.6
- electronnpm
From 39.0.0-alpha.1 · fixed in 39.8.3
- electronnpm
From 40.0.0-alpha.1 · fixed in 40.8.3
- electronnpm
From 41.0.0-alpha.1 · fixed in 41.0.3