CVE-2022-36077

Electron subject to Exfiltration of hashed SMB credentials on Windows via file:// redirect

MEDIUM

6.1

CVSS Score

Published: November 8, 2022 at 12:00 AM UTC

Updated: June 17, 2026 at 04:52 AM UTC

2 products affected across 2 vendorsElectronElectron· also runs on 1 platform

Using electron by electron?

Get instant alerts when new vulnerabilities affect electron - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM6.1

Exploit prediction

EPSS 0.6%

SSVC

No known exploit

Description

The Electron framework enables writing cross-platform desktop applications using JavaScript, HTML and CSS. In versions prior to 21.0.0-beta.1, 20.0.1, 19.0.11, and 18.3.7, Electron is vulnerable to Exposure of Sensitive Information. When following a redirect, Electron delays a check for redirecting to file:// URLs from other schemes. The contents of the file is not available to the renderer following the redirect, but if the redirect target is a SMB URL such as `file://some.website.com/`, then in some cases, Windows will connect to that server and attempt NTLM authentication, which can include sending hashed credentials.This issue has been patched in versions: 21.0.0-beta.1, 20.0.1, 19.0.11, and 18.3.7. Users are recommended to upgrade to the latest stable version of Electron. If upgrading isn't possible, this issue can be addressed without upgrading by preventing redirects to file:// URLs in the `WebContents.on('will-redirect')` event, for all WebContents as a workaround.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Electron · Electronjsnpm

95%

v < 18.3.719.0.0 ≤ v < 19.0.1120.0.0 ≤ v < 20.0.121.0.0 21.0.0 alpha1 21.0.0 alpha2 21.0.0 alpha3 21.0.0 alpha4 21.0.0 alpha5 21.0.0 alpha6

Affected range stops below 18.3.7, so it looks safe — our inference, not a vendor statement

Affected range stops below 19.0.11, so it looks safe — our inference, not a vendor statement

Affected range stops below 20.0.1, so it looks safe — our inference, not a vendor statement

microsoft-windows (environment)

Electron · Electron

60%

v < 18.3.7v < 19.0.11v < 20.0.1v < 21.0.0-beta.1

Affected range stops below 18.3.7, so it looks safe — our inference, not a vendor statement

Affected range stops below 19.0.11, so it looks safe — our inference, not a vendor statement

Affected range stops below 20.0.1, so it looks safe — our inference, not a vendor statement

Affected range stops below 21.0.0-beta.1, so it looks safe — our inference, not a vendor statement

Runs on — not affected

The affected product only carries this flaw when running on these platforms. The platforms themselves are not vulnerable.

Windows · Microsoft

95%

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

https://github.com/electron/electron/security/advisories/GHSA-p2jh-44qj-pf2v

References (1)

MitigationThird Party Advisory

Source: [email protected]

https://github.com/electron/electron/security/advisories/GHSA-p2jh-44qj-pf2v

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

6.1MEDIUM[email protected]

Attack Vector: NETWORK
Complexity: LOW
Privileges: NONE
User Interaction: REQUIRED
Scope: CHANGED
Confidentiality: LOW
Integrity: LOW
Availability: NONE

Vector?

Quick Info

StatusMODIFIED

CWE

CWE-200CWE-522

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create account Sign in

Free plan, no card