GHSA-7m48-wc93-9g85
ASAR Integrity bypass via filetype confusion in electron
Packages
| Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|
| npm | electron | < 22.3.24 | 22.3.24 |
| npm | electron | >= 24.0.0-alpha.1, < 24.8.3 | 24.8.3 |
| npm | electron | >= 25.0.0-alpha.1, < 25.8.1 | 25.8.1 |
| npm | electron | >= 26.0.0-alpha.1, < 26.2.1 | 26.2.1 |
| npm | electron | >= 27.0.0-alpha.1, < 27.0.0-alpha.7 | 27.0.0-alpha.7 |
| npm | electron | >= 23.0.0-alpha.1, <= 23.3.13 | no fix listed |
Details
As written in the advisory (Markdown source, shown as plain text).
### Impact
This only impacts apps that have the `embeddedAsarIntegrityValidation` and `onlyLoadAppFromAsar` [fuses](https://www.electronjs.org/docs/latest/tutorial/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 `resources` folder in your app installation on Windows which these fuses are supposed to protect against.
### Workarounds
There are no app side workarounds, you must update to a patched version of Electron.
### Fixed Versions
* `27.0.0-alpha.7`
* `26.2.1`
* `25.8.1`
* `24.8.3`
* `22.3.24`
### For more information
If you have any questions or comments about this advisory, email us at [[email protected]](mailto:[email protected])
References
External links from the advisory. They lead to third-party sites.