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

> Attackers within radio range can trigger buffer overflows or deadlocks in Cypress PSoC devices via crafted BLE packets, potentially leading to code execution or service disruption.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 10 Feb 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-rpvx-4pph-j4vq

## What is CVE-2019-17061?

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

### Official description

The Bluetooth Low Energy (BLE) stack implementation on Cypress PSoC 4 through 3.62 devices does not properly restrict the BLE Link Layer header and executes certain memory contents upon receiving a packet with a Link Layer ID (LLID) equal to zero. This allows attackers within radio range to cause deadlocks, cause anomalous behavior in the BLE state machine, or trigger a buffer overflow via a crafted BLE Link Layer frame.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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

It affects 1 product.


Products: Cypress Psoc 4 Ble.

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

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

## Is CVE-2019-17061 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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