Electron ASAR Integrity bypass by just modifying the content
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| electron | electron | affected |
|
No data.
No data.
| Vendor | Product | Versions |
|---|---|---|
| Electron | Electron | — |
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2024-54718 | electron ASAR Integrity bypass by just modifying the content |
Github GHSA |
GHSA-xw5q-g62x-2qjc | electron ASAR Integrity bypass by just modifying the content |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.117% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Electron is an open source framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. From versions 30.0.0-alpha.1 to before 30.0.5 and 31.0.0-alpha.1 to before 31.0.0-beta.1, Electron is vulnerable to an ASAR Integrity bypass. 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 Windows, apps using these fuses on macOS are not impacted. Specifically this issue can only be exploited if the 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. This issue has been patched in versions 30.0.5 and 31.0.0-beta.1. There are no workarounds for this issue. | |
| Title | Electron ASAR Integrity bypass by just modifying the content | |
| Weaknesses | CWE-354 | |
| References |
| |
| Metrics |
cvssV3_1
|