Skip to content
Fencer Intel
high 8.8

CVE-2020-10370 json

Certain Cypress (and Broadcom) Wireless Combo chips such as CYW43455, when a 2021-01-26 Bluetooth firmware update is not present, allow a B…

published last yr. modified 4mo ago also EUVD-2020-2825

cvss
8.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 47%
public exploits
0
none known

Summary

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.

Patch / fix

  • bcm43xx-firmware openSUSE Tumbleweed 20180314-14.1

opensuse advisories openSUSE-SU-2024:11689-1

Is CVE-2020-10370 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-10370 updated cvss 5.8

Bluez: bluetooth firmware has Sweyntooth and Spectra issues

  • Red Hat Enterprise Linux 6 bluez, bluez-alsa, bluez-cups, bluez-libs, bluez-compat, bluez-gstreamer Red Hat Enterprise Linux 7 bluez, bluez-cups, bluez-libs, bluez-hid2hci Red Hat Enterprise Linux 8 bluez, bluez-cups, bluez-libs, bluez-obexd, bluez-hid2hci Red Hat Enterprise Linux 9 bluez, bluez-cups, bluez-libs, bluez-obexd
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
last yr.

Exploit prediction

0.57% chance of exploitation in the next 30 days, higher than 47% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CISA ADP 3.1 8.8 CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA 3.1 8.8 CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.