CVE-2022-21718
Published: 22 March 2022
Summary
CVE-2022-21718 is a low-severity Exposure of Resource to Wrong Sphere (CWE-668) vulnerability in Electronjs Electron. Its CVSS base score is 3.4 (Low).
Operationally, ranked in the top 24.7% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2022-1290
Vulnerability details
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…
more
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.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Mandates authorization checks before permitting access or data processing via external systems.
The control provides a mechanism for authorized users to determine authorization matches, preventing sharing without proper authorization verification.
Restricts information flows to ensure resources are not exposed to incorrect or unauthorized spheres.
Requiring explicit authorization for each internal connection prevents missing authorization.
Asset tracking reveals resources that have inadvertently entered an unintended security sphere, permitting corrective isolation.
Enforces separation so resources are not placed in a public sphere without explicit protection.
The control ensures resources are not exposed outside their intended security domain by filtering transfers at the domain boundary.
Internal resources are kept in separate network spheres from externally accessible components.