CVE-2024-45431

The OpenSynergy BlueSDK (also known as Blue SDK ) through version 6.x and prior contains an Improper Input Validation flaw within its Bluetooth stack. The root cause is the failure to properly validate the remote L2CAP channel ID (CID) . An attacker can exploit this vulnerability to bypass existi...

PT-2025-29083

Name of the Vulnerable Software and Affected Versions: OpenSynergy BlueSDK versions through 6.x Description: The OpenSynergy BlueSDK Bluetooth stack contains an incorrect control flow scoping issue. The flaw is due to improper handling of exceptional conditions and a lack of proper return control...

Design/Logic Flaw

The L2CAP signaling channel implementation and SDP server implementation in OpenSynergy Blue SDK 3.2 through 6.0 allow remote, unauthenticated attackers to execute arbitrary code or cause a denial of service via malicious L2CAP configuration requests, in conjunction with crafted SDP communication...

CVE-2018-20378

The L2CAP signaling channel implementation and SDP server implementation in OpenSynergy Blue SDK 3.2 through 6.0 allow remote, unauthenticated attackers to execute arbitrary code or cause a denial of service via malicious L2CAP configuration requests, in conjunction with crafted SDP communication...

CVE-2018-20378

CVE-2018-20378 affects OpenSynergy Blue SDK versions 3.2–6.0, where the L2CAP signaling channel and SDP server allow remote, unauthenticated attackers to execute arbitrary code or cause a denial of service via malicious L2CAP configuration requests, when coupled with crafted SDP traffic over misc...

CVE-2018-20378

The L2CAP signaling channel implementation and SDP server implementation in OpenSynergy Blue SDK 3.2 through 6.0 allow remote, unauthenticated attackers to execute arbitrary code or cause a denial of service via malicious L2CAP configuration requests, in conjunction with crafted SDP communication...

CVE-2018-20378: Improper Input Validation

The L2CAP signaling channel implementation and SDP server implementation in OpenSynergy Blue SDK 3.2 through 6.0 allow remote, unauthenticated attackers to execute arbitrary code or cause a denial of service via malicious L2CAP configuration requests, in conjunction with crafted SDP communication...