Approved changes feed: RSS · Atom

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

part: a version: 6.3.0 update: alpha4

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 NVD CPE 2.0 feed

PURL mappings

PURLSourceLast updated
pkg:github/electron-userland/electron-builder purl2cpe 2026-06-01 10:16:43.076540
pkg:npm/electron-builder purl2cpe 2026-06-01 10:16:43.076541

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2024-39698 vulnerable 2026-06-08 06:41:51.415075 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

Contribute

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