Invalid L2CAP channel creation via null remote CID
Published Sep 12, 2025 · Updated Sep 12, 2025
Improper input validation in OpenSynergy BlueSDK through 6.x allows physically proximate attackers to create a null-CID L2CAP channel. The Bluetooth stack accepts a remote L2CAP channel identifier of zero instead of rejecting the reserved null value during channel creation. Reachability requires Bluetooth proximity and, on the tested devices, pairing approval; the flaw establishes an invalid channel state rather than standalone code execution.
Summary
What happened
Improper input validation in OpenSynergy BlueSDK through 6.x allows physically proximate attackers to create a null-CID L2CAP channel. The Bluetooth stack accepts a remote L2CAP channel identifier of zero instead of rejecting the reserved null value during channel creation. Reachability requires Bluetooth proximity and, on the tested devices, pairing approval; the flaw establishes an invalid channel state rather than standalone code execution.
The record
- CVE
- CVE-2024-45431
- Published
- Sep 12, 2025
- Updated
- Sep 12, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-20
- Attack vector
- adjacent
- Privileges
- Unavailable
Timeline
How it unfolded
- Jun 19, 2024Exploitation reportedPerfektBlue exploit-chain validation
- Sep 12, 2025CVE publishedPublication date reported by the CVE source.
- Sep 12, 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.
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.
Reported exploitation
- PerfektBlue exploit-chain validationexploit chain
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