Skip to content

electron ASAR Integrity bypass by just modifying the content

High severity GitHub Reviewed Published Jun 30, 2025 in electron/electron • Updated Jul 1, 2025

Package

npm electron (npm)

Affected versions

>= 30.0.0-alpha.1, < 30.0.5
>= 31.0.0-alpha.1, < 31.0.0-beta.1

Patched versions

30.0.5
31.0.0-beta.1

Description

electron's ASAR Integrity can be bypass by modifying the content.

Impact

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 unimpacted.

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.

Workarounds

There are no app side workarounds, you must update to a patched version of Electron.

Fixed Versions

  • 30.0.5
  • 31.0.0-beta.1

For more information

If you have any questions or comments about this advisory, email us at [email protected]

References

@VerteDinde VerteDinde published to electron/electron Jun 30, 2025
Published to the GitHub Advisory Database Jun 30, 2025
Reviewed Jun 30, 2025
Published by the National Vulnerability Database Jul 1, 2025
Last updated Jul 1, 2025

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(0th percentile)

Weaknesses

CVE ID

CVE-2024-46992

GHSA ID

GHSA-xw5q-g62x-2qjc

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.