CVE-2023-44402
Assigner: GitHub_M
Published: 2023-12-01T21:45:18.379Z
State: PUBLISHED
title: ASAR Integrity bypass via filetype confusion in electron
problemTypes: descriptions: cweId: CWE-345
description: CWE-345: Insufficient Verification of Data Authenticity
type: CWE
metrics: cvssV3_1: attackComplexity: LOW
attackVector: LOCAL
availabilityImpact: LOW
baseScore: 6.1
baseSeverity: MEDIUM
confidentialityImpact: LOW
integrityImpact: HIGH
privilegesRequired: LOW
scope: UNCHANGED
userInteraction: REQUIRED
vectorString: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:H/A:L
version: 3.1
affected: vendor: electron
product: electron
versions: version: < 22.3.24
status: affected
version: >= 23.0.0-alpha.1, <= 23.3.13
status: affected
version: >= 24.0.0-alpha.1, < 24.8.3
status: affected
version: >= 25.0.0-alpha.1, < 25.8.1
status: affected
version: >= 26.0.0-alpha.1, < 26.2.1
status: affected
version: >= 27.0.0-alpha.1, < 27.0.0-alpha.7
status: affected
descriptions: value: Electron 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.
source: advisory: GHSA-7m48-wc93-9g85
discovery: UNKNOWN