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

> Attackers in radio range can cause a buffer overflow in NXP KW41Z devices via crafted Bluetooth packets, potentially leading to code execution or denial of service.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/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:** 12 Feb 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-5mcg-w6rc-w6jr

## What is CVE-2019-17519?

CVE-2019-17519 is a high-severity memory corruption vulnerability in n/a, published on 12 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 NXP SDK through 2.2.1 for KW41Z devices does not properly restrict the Link Layer payload length, allowing attackers in radio range to cause a buffer overflow via a crafted packet.

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

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

It affects 1 product.


Products: Nxp Mcuxpresso Software Development Kit.

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

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

## Is CVE-2019-17519 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-38258](https://insights.sbomify.com/CVE-2021-38258/): Memory corruption in n/a (high 7.8)
- [CVE-2021-38260](https://insights.sbomify.com/CVE-2021-38260/): Memory corruption in n/a (high 7.8)
- [CVE-2021-27421](https://insights.sbomify.com/CVE-2021-27421/): NXP MCUXpresso SDK Integer Overflow or Wraparound (high 7.3)
- [CVE-2019-17060](https://insights.sbomify.com/CVE-2019-17060/): Memory corruption in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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