Approved changes feed: RSS · Atom

cpe:2.3:a:electron:electron-builder:*:*:*:*:*:node.js:*:*

part: a version: * update: *

VendorElectron (5ca2aa8a-bbaf-518c-9266-2dfdc166f73d)
ProductElectron Builder (e5c61022-b53e-5f6a-8432-063e0ad889c3)
Edition*
Language*
Software edition*
Target softwarenode.js
Target hardware*
Other*
NotesImported from gcve-enriched-dumps CVE data

PURL mappings

PURLSourceLast updated
No PURL mappings for this CPE yet.

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2024-39698 vulnerable 2026-06-08 06:41:51.412126 Code Signing Bypass on Windows in electron-updater < 6.3.0-alpha.6
HIGH (7.5)
electron-updater allows for automatic updates for Electron apps. The file `packages/electron-updater/src/windowsExecutableCodeSignatureVerifier.ts` implements the signature validation routine for Electron applications on Windows. Because of the surrounding shell, a first pass by `cmd.exe` expands any environment variable found in command-line above. This creates a situation where `verifySignature()` can be tricked into validating the certificate of a different file than the one that was just downloaded. If the step is successful, the malicious update will be executed even if its signature is invalid. This attack assumes a compromised update manifest (server compromise, Man-in-the-Middle attack if fetched over HTTP, Cross-Site Scripting to point the application to a malicious updater server, etc.). The patch is available starting from 6.3.0-alpha.6.
Published: 2024-07-09T17:50:28.169Z
Updated: 2024-08-02T04:26:15.985Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-27303 vulnerable 2026-06-08 06:31:28.475174 electron-builder's NSIS installer - execute arbitrary code on the target machine (Windows only)
HIGH (7.3)
electron-builder is a solution to package and build a ready for distribution Electron, Proton Native app for macOS, Windows and Linux. A vulnerability that only affects eletron-builder prior to 24.13.2 in Windows, the NSIS installer makes a system call to open cmd.exe via NSExec in the `.nsh` installer script. NSExec by default searches the current directory of where the installer is located before searching `PATH`. This means that if an attacker can place a malicious executable file named cmd.exe in the same folder as the installer, the installer will run the malicious file. Version 24.13.2 fixes this issue. No known workaround exists. The code executes at the installer-level before the app is present on the system, so there's no way to check if it exists in a current installer.
Published: 2024-03-06T18:35:37.973Z
Updated: 2024-08-13T17:12:24.776Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.