CVE-2020-3911 json
A buffer overflow was addressed with improved bounds checking.
published 6y ago modified 4mo ago also EUVD-2020-25176
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.6%
- EPSS 1.6% chance of exploitation in 30 days, percentile 76%
- public exploits
- 0
- none known
Summary
A buffer overflow was addressed with improved bounds checking. This issue is fixed in iOS 13.4 and iPadOS 13.4, macOS Catalina 10.15.4, tvOS 13.4, watchOS 6.2, iTunes for Windows 12.10.5, iCloud for Windows 10.9.3, iCloud for Windows 7.18. Multiple issues in libxml2.
Patch / fix
- Apple iOS iOS 13.4 and iPadOS 13.4
- Apple macOS macOS Catalina 10.15.4
- Apple tvOS tvOS 13.4
- Apple watchOS watchOS 6.2
- Apple iTunes for Windows iTunes for Windows 12.10.5
- Apple iCloud for Windows iCloud for Windows 10.9.3
- Apple iCloud for Windows (Legacy) iCloud for Windows 7.18
Is CVE-2020-3911 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 FencerExploit prediction
1.64% chance of exploitation in the next 30 days, higher than 76% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Affected products
- Apple iOS
- Apple macOS
- Apple tvOS
- Apple watchOS
- Apple iTunes for Windows
- Apple iCloud for Windows
- Apple iCloud for Windows (Legacy)
Classification
- Weakness
-
- CWE-120 Buffer Copy without Checking Size of Input
References
-
support.apple.com
/HT211100
vendor-advisory
-
support.apple.com
/HT211102
vendor-advisory
-
support.apple.com
/HT211101
vendor-advisory
-
support.apple.com
/HT211103
vendor-advisory
-
support.apple.com
/HT211105
vendor-advisory
-
support.apple.com
/HT211106
vendor-advisory
-
support.apple.com
/HT211107
vendor-advisory
Sources
- CVE List CVE-2020-3911
- NVD CVE-2020-3911
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.