AutoUpdater module fails to validate certain nested components of the bundle
Published 16 Jun 2022 · Updated 8 Nov 2023
Affected packages
- Affected
- <15.5.0
- Fixed in
- 15.5.0
npm install electron@15.5.0- Affected
- >=16.0.0 <16.2.0
- Fixed in
- 16.2.0
npm install electron@16.2.0- Affected
- >=17.0.0 <17.2.0
- Fixed in
- 17.2.0
npm install electron@17.2.0- Affected
- >=18.0.0-beta.1 <18.0.0-beta.6
- Fixed in
- 18.0.0-beta.6
npm install electron@18.0.0-beta.6Details
Impact
This vulnerability allows attackers who have control over a given apps update server / update storage to serve maliciously crafted update packages that pass the code signing validation check but contain malicious code in some components.
Please note that this kind of attack would require significant privileges in your own auto updating infrastructure and the ease of that attack entirely depends on your infrastructure security.
Patches
This has been patched and the following Electron versions contain the fix:
18.0.0-beta.617.2.016.2.015.5.0
Workarounds
There are no workarounds for this issue, please update to a patched version of Electron.
For more information
If you have any questions or comments about this advisory, email us at [security@electronjs.org](mailto:security@electronjs.org)
Is GHSA-77xc-hjv8-ww97 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected electron, and gives you the command that fixes it.
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.