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 over maliciously configured L2CAP channels. The attacker must have connectivity over the Bluetooth physical layer, and must be able to send raw L2CAP frames. This is related to L2Cap_HandleConfigReq in core/stack/l2cap/l2cap_sm.c and SdpServHandleServiceSearchAttribReq in core/stack/sdp/sdpserv.c.
                
            References
                    | Link | Resource | 
|---|---|
| https://www.cymotive.com/wp-content/uploads/2019/03/Hell2CAP-0day.pdf | Exploit Third Party Advisory | 
| https://www.opensynergy.com/news/security/bluesdk-advisory2018003/ | Vendor Advisory | 
| https://www.cymotive.com/wp-content/uploads/2019/03/Hell2CAP-0day.pdf | Exploit Third Party Advisory | 
| https://www.opensynergy.com/news/security/bluesdk-advisory2018003/ | Vendor Advisory | 
Configurations
                    Configuration 1 (hide)
| 
 | 
History
                    No history.
Information
                Published : 2019-03-29 15:29
Updated : 2024-11-21 04:01
NVD link : CVE-2018-20378
Mitre link : CVE-2018-20378
CVE.ORG link : CVE-2018-20378
JSON object : View
Products Affected
                opensynergy
- blue_sdk
CWE
                
                    
                        
                        CWE-20
                        
            Improper Input Validation
