Electron: shell.openPath path validation bypass via embedded null byte
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 39.8.6, 40.9.0, 41.1.1, and 42.0.0-beta.1, shell.openPath() did not reject paths containing embedded null bytes. Apps that perform string-only validation of file paths, for example checking the file extension, before passing them to shell.openPath() could be bypassed, allowing an attacker-controlled path to open a different file than the one that passed validation. Apps are only affected if they pass paths derived from untrusted input to shell.openPath() and rely on string-based validation without a filesystem check. This issue is fixed in versions 39.8.6, 40.9.0, 41.1.1, and 42.0.0-beta.1.
From the CVE record · GitHub_M
Electron’s shell.openPath() did not reject paths containing embedded null bytes. An attacker who controls a path passed to this function could cause an app to open a different file than the one that passed validation, but only if the app relies on string-based path validation without a filesystem check.
Check apps using the npm electron package in the affected ranges: versions below 39.8.6, 40.x before 40.9.0, 41.x before 41.1.1, and 42.0.0-alpha.1 through versions before 42.0.0-beta.1.