dbcve.org
IcloudApplication · Apple

CVE-2020-3826

HIGH · 7.8 CVSS v3.1 Published 2020-02-27
Fix available
A fix is available. Upgrade to 6.1.2 / 10.15.3 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 iOS 13.3.1 and iPadOS 13.3.1, macOS Catalina 10.15.3, tvOS 13.3.1, watchOS 6.1.2, iTunes for Windows 12.10.4, iCloud for Windows 11.0, iCloud for Windows 7.17. 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

An out-of-bounds read vulnerability in image processing components across multiple Apple products (iOS, iPadOS, macOS, tvOS, watchOS, iTunes, iCloud for Windows) allows processing of a maliciously crafted image to trigger the vulnerability, potentially leading to arbitrary code execution. The fix implements improved input validation.

MitigationApply the available security updates: iOS 13.3.1 and later, iPadOS 13.3.1 and later, macOS Catalina 10.15.3 and later, tvOS 13.3.1 and later, watchOS 6.1.2 and later, iTunes 12.10.4 and later for Windows, and corresponding iCloud for Windows updates.

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:< 11.0
ItunesApplication
Affected:< 12.10.4
IpadosOperating system
Affected:< 13.3.1
Iphone OsOperating system
Affected:< 13.3.1
Mac Os XOperating system
Affected:< 10.15.3
TvosOperating system
Affected:< 13.3.1
WatchosOperating system
Affected:< 6.1.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 installed Apple products
    Check for iOS/iPadOS devices connected, macOS computers, Apple TV, Apple Watch, Windows with iTunes or iCloud installed. Note each product type present in your environment.
    Affected if Any Apple product from the affected list is present
  2. Check iOS version
    On iPhone/iPad: Settings > General > About > Version. Compare the version number to 13.3.1
    Affected if Version is lower than 13.3.1
  3. Check iPadOS version
    On iPad: Settings > General > About > Version. Compare the version number to 13.3.1
    Affected if Version is lower than 13.3.1
  4. Check macOS version
    On Mac: Apple menu > About This Mac. Compare the version number to 10.15.3 (Catalina 10.15.3)
    Affected if Version is lower than 10.15.3
  5. Check iTunes version on Windows
    Open iTunes > Help > About iTunes. Compare the version number to 12.10.4
    Affected if Version is lower than 12.10.4
  6. Check iCloud for Windows version
    Open iCloud > click the gear icon > About iCloud. Compare the version number to 11.0
    Affected if Version is lower than 11.0

You are affected if any Apple device or software listed above is running a version lower than the specified threshold (iOS/iPadOS <13.3.1, macOS <10.15.3, tvOS <13.3.1, watchOS <6.1.2, iTunes <12.10.4, iCloud <11.0).

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.1.2 / 10.15.3 / 11.0 or later
Fixed in 6.1.210.15.311.0
Interim mitigation

Apply the available security updates: iOS 13.3.1 and later, iPadOS 13.3.1 and later, macOS Catalina 10.15.3 and later, tvOS 13.3.1 and later, watchOS 6.1.2 and later, iTunes 12.10.4 and later for Windows, and corresponding iCloud for Windows updates.

Fix this in Icloud Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing2.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,340
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-3826 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