Skip to content
Fencer Intel
high 8.8

CVE-2020-9800 json

A type confusion issue was addressed with improved memory handling.

published 6y ago modified 4mo ago also EUVD-2020-30579

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

Summary

A type confusion issue was addressed with improved memory handling. This issue is fixed in iOS 13.5 and iPadOS 13.5, tvOS 13.4.5, watchOS 6.2.5, Safari 13.1.1, iTunes 12.10.7 for Windows, iCloud for Windows 11.2, iCloud for Windows 7.19. Processing maliciously crafted web content may lead to arbitrary code execution.

Patch / fix

  • Apple iOS iOS 13.5 and iPadOS 13.5
  • Apple tvOS tvOS 13.4.5
  • Apple watchOS watchOS 6.2.5
  • Apple Safari Safari 13.1.1
  • Apple iTunes for Windows iTunes 12.10.7 for Windows
  • Apple iCloud for Windows iCloud for Windows 11.2
  • Apple iCloud for Windows (Legacy) iCloud for Windows 7.19

Is CVE-2020-9800 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

Exploit prediction

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

CVSS scores

assigned by version score vector
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P

Affected products

  • Apple iOS
  • Apple tvOS
  • Apple watchOS
  • Apple Safari
  • Apple iTunes for Windows
  • Apple iCloud for Windows
  • Apple iCloud for Windows (Legacy)

Classification

Weakness
  • CWE-843 Access of Resource Using Incompatible Type

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.