dbcve.org
ElectronApplication · Electronjs

CVE-2022-21718

MEDIUM · 5.0 CVSS v3.1 Published 2022-03-22
Fix available
A fix is available. Upgrade to 13.6.6 / 14.2.4 or later.
See remediation →
56/100
Remediation priority · Elevated
Remotely reachable Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. A vulnerability in versions prior to `17.0.0-alpha.6`, `16.0.6`, `15.3.5`, `14.2.4`, and `13.6.6` allows renderers to obtain access to a bluetooth device via the web bluetooth API if the app has not configured a custom `select-bluetooth-device` event handler. This has been patched and Electron versions `17.0.0-alpha.6`, `16.0.6`, `15.3.5`, `14.2.4`, and `13.6.6` contain the fix. Code from the GitHub Security Advisory can be added to the app to work around the issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ElectronApplication
Affected:< 13.6.6>= 14.0.0, < 14.2.4>= 15.0.0, < 15.3.5>= 16.0.0, < 16.0.6= 17.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 13.6.6 / 14.2.4 / 15.3.5 or later
Fixed in 13.6.614.2.415.3.5
Vendor patch github.com →
Recommended fix High confidence

Electron 13.6.6 (for 13.x users), 14.2.4 (for 14.x users), 15.3.5 (for 15.x users), or 16.0.6 (for 16.x users) - or migrate to the latest stable release in each respective branch

  1. Identify the current Electron version in use by checking package.json or the electron dependency version
  2. If using Electron 12.x or earlier (< 13.6.6): upgrade to Electron 13.6.6 or later (preferably latest 13.x)
  3. If using Electron 14.x (>= 14.0.0, < 14.2.4): upgrade to Electron 14.2.4 or later (preferably latest 14.x)
  4. If using Electron 15.x (>= 15.0.0, < 15.3.5): upgrade to Electron 15.3.5 or later (preferably latest 15.x)
  5. If using Electron 16.x (>= 16.0.0, < 16.0.6): upgrade to Electron 16.0.6 or later (preferably latest 16.x)
  6. Run npm install electron@<version> or yarn add electron@<version> to update the dependency
  7. Rebuild native modules if needed: npm rebuild or electron-rebuild
  8. Test the application thoroughly, especially any Bluetooth functionality
Caveat Minor/patch updates within the same major version typically have minimal breaking changes, but review the Electron release notes for the target version to check for deprecations or API changes

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-21718 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-21718 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data