IcloudApplication · Apple

CVE-2020-9919

HIGH · 7.8 CVSS v3.1 Published 2020-10-22
Fix available
A fix is available. Upgrade to 6.2.8 / 7.20 or later.
See remediation →
81/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A buffer overflow issue was addressed with improved memory handling. This issue is fixed in iOS 13.6 and iPadOS 13.6, macOS Catalina 10.15.6, tvOS 13.4.8, watchOS 6.2.8, iTunes 12.10.8 for Windows, iCloud for Windows 11.3, iCloud for Windows 7.20. Processing a maliciously crafted image may lead to arbitrary code execution.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A buffer overflow vulnerability in Apple's image processing libraries allows arbitrary code execution when processing a maliciously crafted image. The vulnerability affects multiple Apple operating systems and applications including iOS, iPadOS, macOS, tvOS, watchOS, iTunes, and iCloud for Windows.

MitigationApply available security updates: iOS 13.6/iPadOS 13.6, macOS Catalina 10.15.6, tvOS 13.4.8, watchOS 6.2.8, iTunes 12.10.8 for Windows, iCloud for Windows 11.3/7.20. Where possible, upgrade to later supported OS versions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
IcloudApplication
Affected:< 7.20>= 11.0, < 11.3
ItunesApplication
Affected:< 12.10.8
IpadosOperating system
Affected:< 13.6
Iphone OsOperating system
Affected:< 13.6
Mac Os XOperating system
Affected:< 10.15.6
TvosOperating system
Affected:< 13.4.8
WatchosOperating system
Affected:< 6.2.8

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Apple product and version
    Check the installed version of the Apple software (iOS, iPadOS, macOS, tvOS, watchOS, iTunes, or iCloud for Windows) using system settings, the 'About' menu, or command line tools like 'sw_vers' for macOS
    Affected if The product is one of iOS, iPadOS, macOS, tvOS, watchOS, iTunes, or iCloud for Windows and the version falls below the fixed release
  2. Compare iOS or iPadOS version against affected range
    For iOS or iPadOS devices, go to Settings > General > About > Version to see the installed version number
    Affected if The version is earlier than 13.6
  3. Compare macOS version against affected range
    On macOS, run 'sw_vers' in Terminal or check System Preferences > About to see the macOS version
    Affected if The version is earlier than 10.15.6 (Catalina)
  4. Compare tvOS or watchOS version against affected range
    On Apple TV or Apple Watch, go to Settings > General > About to view the version
    Affected if tvOS is earlier than 13.4.8 or watchOS is earlier than 6.2.8
  5. Compare iTunes or iCloud for Windows version against affected range
    On Windows, open iTunes or iCloud and go to Help > About to see the version number
    Affected if iTunes is earlier than 12.10.8, or iCloud for Windows is earlier than 7.20 or falls between 11.0 and 11.3

The environment is affected if any of the installed Apple products (iOS, iPadOS, macOS, tvOS, watchOS, iTunes, or iCloud for Windows) match the affected version ranges and process untrusted image files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 6.2.8 / 7.20 / 10.15.6 or later
Fixed in 6.2.87.2010.15.6
Interim mitigation

Apply available security updates: iOS 13.6/iPadOS 13.6, macOS Catalina 10.15.6, tvOS 13.4.8, watchOS 6.2.8, iTunes 12.10.8 for Windows, iCloud for Windows 11.3/7.20. Where possible, upgrade to later supported OS versions.

Fix this in Icloud Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-9919 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-9919 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data