# CVE-2019-17520: Denial of service in n/a

> Attackers in radio range can crash Texas Instruments CC2640R2 devices by sending crafted Bluetooth Low Energy SM Public Key packets.

- **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-xr3c-8qvg-wf25

## What is CVE-2019-17520?

CVE-2019-17520 is a medium-severity denial of service 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 implementation on Texas Instruments SDK through 3.30.00.20 for CC2640R2 devices does not properly restrict the SM Public Key packet on reception, allowing attackers in radio range to cause a denial of service (crash) via crafted packets.

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

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

It affects 1 product.


Products: Ti Cc2640r2 Software Development Kit.

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

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

## Is CVE-2019-17520 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-17520 is a medium-severity denial of service 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-17520 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-17520/ (Markdown: https://insights.sbomify.com/CVE-2019-17520/index.md)
```

## Sources

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

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