Unsigned update execution via expanded path variables
Published Jul 9, 2024 · Updated Aug 2, 2024
Code-signing bypass in electron-updater before 6.3.0-alpha.6 allows remote attackers to execute an unsigned Windows update. The verifySignature routine passes an untrusted update path through cmd.exe, whose environment-variable expansion can redirect certificate validation to a different file. Exploitation requires control of the update manifest and causes the downloaded malicious update to run with the application's privileges.
Summary
What happened
Code-signing bypass in electron-updater before 6.3.0-alpha.6 allows remote attackers to execute an unsigned Windows update. The verifySignature routine passes an untrusted update path through cmd.exe, whose environment-variable expansion can redirect certificate validation to a different file. Exploitation requires control of the update manifest and causes the downloaded malicious update to run with the application's privileges.
The record
- CVE
- CVE-2024-39698
- Published
- Jul 9, 2024
- Updated
- Aug 2, 2024
- Vendor
- Electron Userland
- Product
- electron-builder
- Classifications
- CWE-295, CWE-154, T1195.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 9, 2024CVE 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=< 6.3.0-alpha.6
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
- Upstream environment-variable path redirection proof of conceptproof of concept · demonstrated
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