# CVE-2022-46399: Denial of service in n/a

> The Microchip RN4870 Bluetooth module firmware becomes unresponsive when handling a specific connection request timeout, causing a denial of service.

- **Severity:** High 7.5 (`CVSS:3.1/AV:A/AC:H/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:** 19 Dec 2022
- **Updated:** 17 Apr 2025
- **Also known as:** GHSA-6w9r-9p3m-qrj9

## What is CVE-2022-46399?

CVE-2022-46399 is a high-severity denial of service vulnerability in n/a, published on 19 Dec 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Microchip RN4870 module firmware 1.43 (and the Microchip PIC LightBlue Explorer Demo 4.2 DT100112) is unresponsive with ConReqTimeoutZero.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2022-46399?

It affects 14 products.


Products: Microchip Bm64 Firmware, Microchip Bm70 Firmware, Microchip Bm71 Firmware, Microchip Bm77 Firmware, Microchip Bm78 Firmware, Microchip Bm83 Firmware, Microchip Is1870 Firmware, Microchip Is1871 Firmware, Microchip Pic32cx1012bz25048 Firmware, Microchip Pic Lightblue Explorer Demo Firmware, Microchip Rn4678 Firmware, Microchip Rn4870 Firmware, Microchip Rn4871 Firmware, Microchip Wbz451 Firmware.

## How do I fix CVE-2022-46399?

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

## Is CVE-2022-46399 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-46401](https://insights.sbomify.com/CVE-2022-46401/): Security feature bypass in n/a (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-46399 and fix it if it is affected.

What it is: CVE-2022-46399 is a high-severity denial of service vulnerability in n/a, published on 19 Dec 2022. 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-2022-46399 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-2022-46399/ (Markdown: https://insights.sbomify.com/CVE-2022-46399/index.md)
```

## Sources

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

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