Skip to main content
No exploitation reportedFix available

CVE-2018-20378

No exploitation reported by the sources we read.

  • Published2019-03-29
  • Fixed in6.0.1
  • WeaknessCWE-20

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2019-03-2915:29CVE publishedNVD

Versions per branch

NVD
Opensynergy blue sdk
BranchAffectedFixed in
6.0≥ 6.0, < 6.0.16.0.1
5.5≥ 3.2, ≤ 5.5.3no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

  1. Update Opensynergy blue sdk to 6.0.1

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.0/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Published
2019-03-29
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-v7p7-43jq-569f

Frequently asked questions

What is 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 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.

Is CVE-2018-20378 actively exploited?

Active exploitation of CVE-2018-20378 has not been confirmed. Its EPSS score was 2.3% on 2026-11-08, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2018-20378?

CVE-2018-20378 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.0/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record