ASAR Integrity bypass via filetype confusion in electron
electron
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| electron npm |
|
|
electron
| Product | Affected | Fixed in |
|---|---|---|
| electron npm |
|
|
25.8.126.2.127.0.0-alpha.7Electron is an open source framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. This only impacts apps that have the `embeddedAsarIntegrityValidation` and `onlyLoadAppFromAsar` fuses enabled. Apps without these fuses enabled are not impacted. This issue is specific to macOS as these fuses are only currently supported on macOS. Specifically this issue can only be exploited if your app is launched from a filesystem the attacker has write access too. i.e. the ability to edit files inside the `.app` bundle on macOS which these fuses are supposed to protect against. There are no app side workarounds, you must update to a patched version of Electron.
From the CVE record · GitHub_M
On macOS, Electron apps with both `embeddedAsarIntegrityValidation` and `onlyLoadAppFromAsar` enabled are affected. An attacker can edit files inside the `.app` bundle despite those protections if the app is launched from a filesystem the attacker can write to. Apps without both fuses enabled are not affected.
Check macOS apps using npm `electron` versions below 22.3.24, 24.0.0-alpha.1 through versions below 24.8.3, 25.0.0-alpha.1 through versions below 25.8.1, 26.0.0-alpha.1 through versions below 26.2.1, 27.0.0-alpha.1 through versions below 27.0.0-alpha.7, or 23.0.0-alpha.1 through 23.3.13.