# CVE-2020-10370: Denial of service in n/a

> Attackers can cause Bluetooth outages on Cypress and Broadcom wireless chips by exploiting a Spectra attack if the firmware is not updated.

- **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:** Yes
- **Published:** 10 Nov 2024
- **Updated:** 27 Jan 2025
- **Also known as:** GHSA-x8m2-f296-h7vh, UBUNTU-CVE-2020-10370, openSUSE-SU-2024:11689-1

## What is CVE-2020-10370?

CVE-2020-10370 is a high-severity denial of service vulnerability in n/a, published on 10 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Certain Cypress (and Broadcom) Wireless Combo chips such as CYW43455, when a 2021-01-26 Bluetooth firmware update is not present, allow a Bluetooth outage via a "Spectra" attack.

## Which versions are affected by CVE-2020-10370?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `bcm43xx-firmware` | openSUSE:Tumbleweed | All versions | 20180314-14.1 |

## How do I fix CVE-2020-10370?

Apply the vendor's patch.

## Is CVE-2020-10370 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-10370 and fix it if it is affected.

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

## Sources

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

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