CVE-2020-9770 json
A logic issue was addressed with improved state management.
published 6y ago modified 4mo ago also EUVD-2020-30549
- cvss
- 6.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 68%
- public exploits
- 0
- none known
Summary
A logic issue was addressed with improved state management. This issue is fixed in iOS 13.4 and iPadOS 13.4. An attacker in a privileged network position may be able to intercept Bluetooth traffic.
Patch / fix
- Apple iOS iOS 13.4 and iPadOS 13.4
Is CVE-2020-9770 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 FencerVendor 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-9770 updated cvss 6.6
bluez: BLESA bluetooth attack
-
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-hid2hciaffected: workaround, no fix planned “Will not fix”
-
Red Hat Enterprise Linux 9 bluez, bluez-cups, bluez-libs, bluez-obexdaffected: workaround, no fix available
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
Exploit prediction
1.20% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:P/I:N/A:N |
Affected products
- Apple iOS
References
-
support.apple.com
/HT211102
vendor-advisory
Sources
- CVE List CVE-2020-9770
- NVD CVE-2020-9770
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.