For your digest
electron: Renderers can obtain access to random bluetooth device without permission in Electron
It touches something Phylax follows. No evidence of use yet.
Does it affect what I run?
electron (npm)
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- electron (npm): every version, before 13.6.6
- electron (npm): from 14.0.0-beta.1, before 14.2.4
- electron (npm): from 15.0.0-beta.1, before 15.3.5
- electron (npm): from 16.0.0-beta.1, before 16.0.6
- electron (npm): from 17.0.0-alpha.1, before 17.0.0-alpha.6
The fix
electron (npm) fixed in 13.6.6
npmnpm install electron@13.6.6pnpmpnpm add electron@13.6.6yarnyarn add electron@13.6.6bunbun add electron@13.6.6Check what is installednpm ls electronPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency electron to 13.6.6 or the nearest later release, to fix CVE-2022-21718. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.electron (npm) fixed in 14.2.4
npmnpm install electron@14.2.4pnpmpnpm add electron@14.2.4yarnyarn add electron@14.2.4bunbun add electron@14.2.4Check what is installednpm ls electronPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency electron to 14.2.4 or the nearest later release, to fix CVE-2022-21718. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.electron (npm) fixed in 15.3.5
npmnpm install electron@15.3.5pnpmpnpm add electron@15.3.5yarnyarn add electron@15.3.5bunbun add electron@15.3.5Check what is installednpm ls electronPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency electron to 15.3.5 or the nearest later release, to fix CVE-2022-21718. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.electron (npm) fixed in 16.0.6
npmnpm install electron@16.0.6pnpmpnpm add electron@16.0.6yarnyarn add electron@16.0.6bunbun add electron@16.0.6Check what is installednpm ls electronPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency electron to 16.0.6 or the nearest later release, to fix CVE-2022-21718. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.electron (npm) fixed in 17.0.0-alpha.6
npmnpm install electron@17.0.0-alpha.6pnpmpnpm add electron@17.0.0-alpha.6yarnyarn add electron@17.0.0-alpha.6bunbun add electron@17.0.0-alpha.6Check what is installednpm ls electronPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency electron to 17.0.0-alpha.6 or the nearest later release, to fix CVE-2022-21718. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
Fix commands generated from the advisory's versions. No model wrote them.
In plain words
Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.
Evidence
No evidence that it is being used, or can be. It is listed because of what it affects.
Timeline
- First published here, as "For your digest".