# CVE-2019-18614: Memory corruption in n/a

> A buffer overflow in Cypress CYW20735 Bluetooth firmware allows remote code execution or denial of service via oversized packets.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jun 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-2hf8-gw5c-2f9c

## What is CVE-2019-18614?

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

### Official description

On the Cypress CYW20735 evaluation board, any data that exceeds 384 bytes is copied and causes an overflow. This is because the maximum BLOC buffer size for sending and receiving data is set to 384 bytes, but everything else is still configured to the usual size of 1092 (which was used for everything in the previous CYW20719 and later CYW20819 evaluation board). To trigger the overflow, an attacker can either send packets over the air or as unprivileged local user. Over the air, the minimal PoC is sending "l2ping -s 600" to the target address prior to any pairing. Locally, the buffer overflow is immediately triggered by opening an ACL or SCO connection to a headset. This occurs because, in WICED Studio 6.2 and 6.4, BT_ACL_HOST_TO_DEVICE_DEFAULT_SIZE and BT_ACL_DEVICE_TO_HOST_DEFAULT_SIZE are set to 384.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2019-18614?

It affects 1 product.


Products: Cypress Cyw20735 Firmware.

## How do I fix CVE-2019-18614?

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

## Is CVE-2019-18614 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-18614 and fix it if it is affected.

What it is: CVE-2019-18614 is a high-severity memory corruption vulnerability in n/a, published on 16 Jun 2020. 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-2019-18614 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-2019-18614/ (Markdown: https://insights.sbomify.com/CVE-2019-18614/index.md)
```

## Sources

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

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