Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm

GHSA-7m48-wc93-9g85

MEDIUM

ASAR Integrity bypass via filetype confusion in electron

Also known asCVE-2023-44402
Published
Dec 1, 2023
Updated
Sep 18, 2024
Affected
6 pkgs
Patched
5 / 6
Exploits
None indexed

EPSS Exploitation Probability

via FIRST.org ↗
0.2%probability of exploitation in next 30 days
Lower Risk11th percentile+0.09%
0.00%0.24%0.47%0.71%0.0%0.2%Dec 25Apr 26Jun 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

6 pkgs affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

electronnpm
4.8Mdownloads / week

Description

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 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]

Affected Packages

6 total 5 fixed
EcosystemPackageVulnerable rangeFix
📦npmelectronall versions22.3.24
📦npmelectron24.0.0-alpha.1&&< 24.8.324.8.3
📦npmelectron25.0.0-alpha.1&&< 25.8.125.8.1
📦npmelectron26.0.0-alpha.1&&< 26.2.126.2.1
📦npmelectron27.0.0-alpha.1&&< 27.0.0-alpha.727.0.0-alpha.7
📦npmelectron23.0.0-alpha.1No fix

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for electron. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update electron to 22.3.24 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7m48-wc93-9g85 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-7m48-wc93-9g85 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-7m48-wc93-9g85. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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. ### Wor
O3 Security · Impact-Aware SCA

Is GHSA-7m48-wc93-9g85 in your dependencies?

O3 detects GHSA-7m48-wc93-9g85 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.