Integrity bypass via ASAR filetype confusion
Published Dec 1, 2023 · Updated Aug 2, 2024
Integrity verification bypass in Electron before 22.3.24 and specified 23–27 releases allows local users to alter packaged app resources via filetype confusion. The ASAR loader trusts a path ending in .asar without confirming that the file is a genuine ASAR archive when embeddedAsarIntegrityValidation and onlyLoadAppFromAsar are enabled. Exploitation requires macOS, user write access to the launched .app bundle, and application launch; the result is high-integrity resource tampering with limited confidentiality and availability impact.
Summary
What happened
Integrity verification bypass in Electron before 22.3.24 and specified 23–27 releases allows local users to alter packaged app resources via filetype confusion. The ASAR loader trusts a path ending in .asar without confirming that the file is a genuine ASAR archive when embeddedAsarIntegrityValidation and onlyLoadAppFromAsar are enabled. Exploitation requires macOS, user write access to the launched .app bundle, and application launch; the result is high-integrity resource tampering with limited confidentiality and availability impact.
The record
- CVE
- CVE-2023-44402
- Published
- Dec 1, 2023
- Updated
- Aug 2, 2024
- Vendor
- Electron
- Product
- Electron
- Classifications
- CWE-345, T1565.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 1, 2023CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 22.3.24
- Affected versionversion=>= 23.0.0-alpha.1, <= 23.3.13
- Affected versionversion=>= 24.0.0-alpha.1, < 24.8.3
- Affected versionversion=>= 25.0.0-alpha.1, < 25.8.1
- Affected versionversion=>= 26.0.0-alpha.1, < 26.2.1
- Affected versionversion=>= 27.0.0-alpha.1, < 27.0.0-alpha.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo