Security-level bypass via conjunctive key validation
Published Dec 12, 2022 · Updated Apr 22, 2025
Improper key validation in Zephyr RTOS 3.1 and earlier allows remote attackers to retain Bluetooth keys that fail security requirements. The final condition in smp_check_keys joins three mandatory level-four checks with AND, so it rejects existing keys only when every requirement fails instead of when any requirement fails. The path applies when a connection requires security above level 3; Zephyr has not published the concrete data access, modification, or service interruption enabled.
Summary
What happened
Improper key validation in Zephyr RTOS 3.1 and earlier allows remote attackers to retain Bluetooth keys that fail security requirements. The final condition in smp_check_keys joins three mandatory level-four checks with AND, so it rejects existing keys only when every requirement fails instead of when any requirement fails. The path applies when a connection requires security above level 3; Zephyr has not published the concrete data access, modification, or service interruption enabled.
The record
- CVE
- CVE-2022-2993
- Published
- Dec 12, 2022
- Updated
- Apr 22, 2025
- Vendor
- Zephyr Project
- Product
- Zephyr RTOS
- Classifications
- CWE-670, CWE-20
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 12, 2022CVE publishedPublication date reported by the CVE source.
- Apr 22, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <=v3.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo