Security validation bypass via incorrect RFCOMM termination
Published Sep 12, 2025 · Updated Sep 12, 2025
Incorrect control flow in OpenSynergy BlueSDK through 6.x allows remote attackers to bypass RFCOMM security validation via Bluetooth traffic. The RFCOMM handler detects an unusual condition but fails to return, so subsequent processing accepts incoming data that should have been rejected. The tested automotive deployments required Bluetooth pairing, while exposure before pairing depends on the profile security level or Just Works mode.
Summary
What happened
Incorrect control flow in OpenSynergy BlueSDK through 6.x allows remote attackers to bypass RFCOMM security validation via Bluetooth traffic. The RFCOMM handler detects an unusual condition but fails to return, so subsequent processing accepts incoming data that should have been rejected. The tested automotive deployments required Bluetooth pairing, while exposure before pairing depends on the profile security level or Just Works mode.
The record
- CVE
- CVE-2024-45433
- Published
- Sep 12, 2025
- Updated
- Sep 12, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-705
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 19, 2024Exploitation reportedPerfektBlue automotive infotainment exploit chain
- 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
- PerfektBlue automotive head-unit demonstrationfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Reported exploitation
- PerfektBlue automotive infotainment exploit chainexploit 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