# CVE-2018-20378: Memory corruption in n/a

> Remote attackers with Bluetooth proximity can execute arbitrary code or cause denial of service in OpenSynergy Blue SDK via malicious L2CAP and SDP requests.

- **Severity:** High 7.5 (`CVSS:3.0/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Mar 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-v7p7-43jq-569f

## What is CVE-2018-20378?

CVE-2018-20378 is a high-severity memory corruption vulnerability in n/a, published on 29 Mar 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2018-20378?

It affects 1 product.


Products: Opensynergy Blue Sdk.

## How do I fix CVE-2018-20378?

No fix has been published for CVE-2018-20378 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-20378 being exploited?

There is no known exploitation of CVE-2018-20378 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2024-45434](https://insights.sbomify.com/CVE-2024-45434/): Use after free in n/a (critical 9.8)
- [CVE-2024-45432](https://insights.sbomify.com/CVE-2024-45432/): Information disclosure in n/a (high 7.5)
- [CVE-2024-45433](https://insights.sbomify.com/CVE-2024-45433/): Security feature bypass in n/a (medium 6.5)
- [CVE-2024-45431](https://insights.sbomify.com/CVE-2024-45431/): Other in n/a (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-20378 and fix it if it is affected.

What it is: CVE-2018-20378 is a high-severity memory corruption vulnerability in n/a, published on 29 Mar 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-20378 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-20378/ (Markdown: https://insights.sbomify.com/CVE-2018-20378/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-20378
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-20378
- OSV: https://osv.dev/vulnerability/CVE-2018-20378

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-20378/
Summaries are generated and may contain mistakes; the official description above is the record.