Memory corruption via unchecked provisioning segment count
Published Feb 1, 2023 · Updated Mar 27, 2025
Buffer overflow in Bestechnic Bluetooth Mesh SDK 1.0 for BES2300 allows physically proximate attackers to corrupt memory during provisioning. The provisioning code accepts the Transaction Start PDU's SegN field without checking it against the available segment buffer. Bluetooth proximity and an active provisioning exchange are required; published sources do not establish whether exploitation causes a crash or code execution.
Summary
What happened
Buffer overflow in Bestechnic Bluetooth Mesh SDK 1.0 for BES2300 allows physically proximate attackers to corrupt memory during provisioning. The provisioning code accepts the Transaction Start PDU's SegN field without checking it against the available segment buffer. Bluetooth proximity and an active provisioning exchange are required; published sources do not establish whether exploitation causes a crash or code execution.
The record
- CVE
- CVE-2022-30904
- Published
- Feb 1, 2023
- Updated
- Mar 27, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787
- Attack vector
- adjacent
- Privileges
- Unavailable
Timeline
How it unfolded
- Feb 1, 2023CVE publishedPublication date reported by the CVE source.
- Mar 27, 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