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

> Attackers in radio range can cause a deadlock or crash on STM32WB5x devices by sending crafted Bluetooth Low Energy 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:** 12 Feb 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-qc6w-j34c-8p2x

## What is CVE-2019-19192?

CVE-2019-19192 is a medium-severity denial of service 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 STMicroelectronics BLE Stack through 1.3.1 for STM32WB5x devices does not properly handle consecutive Attribute Protocol (ATT) requests on reception, allowing attackers in radio range to cause an event deadlock or crash via crafted packets.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 2 products.


Products: St Bluenrg-2, St Wb55.

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

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

## Is CVE-2019-19192 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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