Pairing interoperability failure via inconsistent reject timing
Published Dec 19, 2022 · Updated Apr 17, 2025
Improper reject handling in Microchip RN4870 firmware 1.43 and PIC LightBlue Explorer Demo 4.2 DT100112 disrupts BLE pairing. During Secure Connections public-key exchange, implementations reject an invalid PublicKeySend at inconsistent protocol stages or fail to reject it. The issue is limited to pairing interoperability; the research classifies it as a specification ambiguity rather than an exploitable attack.
Summary
What happened
Improper reject handling in Microchip RN4870 firmware 1.43 and PIC LightBlue Explorer Demo 4.2 DT100112 disrupts BLE pairing. During Secure Connections public-key exchange, implementations reject an invalid PublicKeySend at inconsistent protocol stages or fail to reject it. The issue is limited to pairing interoperability; the research classifies it as a specification ambiguity rather than an exploitable attack.
The record
- CVE
- CVE-2022-46403
- Published
- Dec 19, 2022
- Updated
- Apr 17, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-755
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 19, 2022CVE publishedPublication date reported by the CVE source.
- Apr 17, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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