IcloudApplication · Apple

CVE-2020-29619

HIGH · 7.8 CVSS v3.1 Published 2021-04-02
Fix available
A fix is available. Upgrade to 7.2 / 10.14.6 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
An out-of-bounds read was addressed with improved input validation. This issue is fixed in tvOS 14.3, macOS Big Sur 11.1, Security Update 2020-001 Catalina, Security Update 2020-007 Mojave, iOS 14.3 and iPadOS 14.3, iCloud for Windows 12.0, watchOS 7.2. Processing a maliciously crafted image may lead to heap corruption.

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

An out-of-bounds read vulnerability in Apple's image processing components allows heap corruption when processing a maliciously crafted image file. The vulnerability is caused by insufficient input validation during image parsing, leading to memory corruption that could be exploited for arbitrary code execution.

MitigationApply the available security updates: iOS 14.3/iPadOS 14.3, macOS Big Sur 11.1/Catalina Security Update 2020-001/Mojave Security Update 2020-007, tvOS 14.3, watchOS 7.2, and iCloud for Windows 12.0.

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:< 12.0
IpadosOperating system
Affected:< 14.3
Iphone OsOperating system
Affected:< 14.3
Mac Os XOperating system
Affected:>= 10.14, < 10.14.6>= 10.15, < 10.15.7= 10.14.6= 10.15.7
macOSOperating system
Affected:>= 11.0, < 11.1.0
TvosOperating system
Affected:< 14.3
WatchosOperating system
Affected:< 7.2

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 in use
    Determine whether the system is running macOS, iOS, iPadOS, tvOS, watchOS, or iCloud for Windows. On macOS, go to Apple menu > About This Mac. On iOS/iPadOS, go to Settings > General > About. On tvOS/watchOS, go to Settings > General > About. For iCloud, check the iCloud application version on Windows.
    Affected if Any Apple product from the affected list is in use.
  2. Check the installed macOS version
    On macOS, run 'sw_vers' in Terminal or check Apple menu > About This Mac. Note the exact version number (e.g., 11.0.1, 10.15.7, 10.14.6).
    Affected if The version is: macOS Big Sur 11.0 to 11.0.x before 11.1; macOS Catalina 10.15.0 to 10.15.7 (including 10.15.7); macOS Mojave 10.14.0 to 10.14.6 (including 10.14.6).
  3. Check the installed iOS or iPadOS version
    On iPhone or iPad, go to Settings > General > About and note the version number (e.g., 14.2, 14.2.1).
    Affected if The version is iOS or iPadOS earlier than 14.3.
  4. Check the installed tvOS or watchOS version
    On Apple TV, go to Settings > General > About > Version. On Apple Watch, go to Settings > General > About > Watch Version. Note the version number.
    Affected if The version is tvOS earlier than 14.3 or watchOS earlier than 7.2.
  5. Check the installed iCloud for Windows version
    Open iCloud for Windows, click the menu or gear icon, and check About iCloud, or open Programs and Features in Windows Control Panel and find iCloud.
    Affected if The version is iCloud for Windows earlier than 12.0.

The environment is affected if any Apple product listed is installed and its version falls within the affected ranges: iCloud < 12.0, iPadOS < 14.3, iOS < 14.3, macOS (including older Mac OS X naming) versions 10.14.x up to 10.14.6, 10.15.x up to 10.15.7, or 11.0.x up to 11.0.x before 11.1, tvOS < 14.3, or watchOS < 7.2.

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 7.2 / 10.14.6 / 10.15.7 or later
Fixed in 7.210.14.610.15.7
Interim mitigation

Apply the available security updates: iOS 14.3/iPadOS 14.3, macOS Big Sur 11.1/Catalina Security Update 2020-001/Mojave Security Update 2020-007, tvOS 14.3, watchOS 7.2, and iCloud for Windows 12.0.

Fix this in Icloud Scoped from the published advisory
  • Consultation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
3.0 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-29619 — 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-29619 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