CVE-2020-36521 json
An out-of-bounds read was addressed with improved input validation.
published 4y ago modified 4mo ago also EUVD-2020-23998
- cvss
- 7.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 38%
- public exploits
- 0
- none known
Summary
An out-of-bounds read was addressed with improved input validation. This issue is fixed in iCloud for Windows 11.4, iOS 14.0 and iPadOS 14.0, watchOS 7.0, tvOS 14.0, iCloud for Windows 7.21, iTunes for Windows 12.10.9. Processing a maliciously crafted tiff file may lead to a denial-of-service or potentially disclose memory contents.
Patch / fix
- Apple iTunes for Windows 12.10
- Apple iOS and iPadOS 14.0
- Apple iCloud for Windows 7.21, 11.4
- Apple watchOS 7.0, 14.0
Is CVE-2020-36521 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 FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.44% chance of exploitation in the next 30 days, higher than 38% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 7.1 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H |
| NVD | 3.1 | 7.1 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H |
| CNA | 3.1 | 7.1 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H |
Affected products
- Apple iTunes for Windows
- Apple iOS and iPadOS
- Apple iCloud for Windows
- Apple watchOS
Classification
- Weakness
-
- CWE-125 Out-of-bounds Read
References
-
support.apple.com
/en-us/HT211843
vendor-advisory
-
support.apple.com
/en-us/HT211850
vendor-advisory
-
support.apple.com
/en-us/HT211844
vendor-advisory
-
support.apple.com
/en-us/HT211952
vendor-advisory
-
support.apple.com
/en-us/HT211847
vendor-advisory
-
support.apple.com
/en-us/HT211846
vendor-advisory
Sources
- CVE List CVE-2020-36521
- NVD CVE-2020-36521
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.