Confidentiality compromise via reflected OOB public key
Published Sep 25, 2023 · Updated Sep 24, 2024
Incorrect Bluetooth Mesh provisioning in Zephyr RTOS before 3.4 allows physically proximate attackers to compromise confidentiality. The prov_pub_key() path accepts a received provisioner key even when it is identical to the provisionee's configured OOB public key, defeating the required rejection. Exposure requires OOB public-key support on an unprovisioned device during a nearby provisioning exchange; published sources do not identify the specific data disclosed.
Summary
What happened
Incorrect Bluetooth Mesh provisioning in Zephyr RTOS before 3.4 allows physically proximate attackers to compromise confidentiality. The prov_pub_key() path accepts a received provisioner key even when it is identical to the provisionee's configured OOB public key, defeating the required rejection. Exposure requires OOB public-key support on an unprovisioned device during a nearby provisioning exchange; published sources do not identify the specific data disclosed.
The record
- CVE
- CVE-2023-4258
- Published
- Sep 25, 2023
- Updated
- Sep 24, 2024
- Vendor
- Zephyr Project
- Product
- Zephyr RTOS
- Classifications
- CWE-684, T1557
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 25, 2023CVE publishedPublication date reported by the CVE source.
- Sep 24, 2024Record 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=0 <3.4
- Affected versionversion=1.14 <=3.4
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