dbcve.org
IcloudApplication · Apple

CVE-2020-10002

MEDIUM · 5.5 CVSS v3.1 Published 2020-12-08
Fix available
A fix is available. Upgrade to 7.1 / 10.14.6 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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 logic issue was addressed with improved state management. This issue is fixed in macOS Big Sur 11.0.1, watchOS 7.1, iOS 14.2 and iPadOS 14.2, iCloud for Windows 11.5, tvOS 14.2, iTunes 12.11 for Windows. A local user may be able to read arbitrary files.

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

CVE-2020-10002 is a logic flaw in multiple Apple products (macOS, iOS, iPadOS, watchOS, tvOS, iCloud for Windows, iTunes for Windows) where improper state management allows a local authenticated user to bypass restrictions and read arbitrary files on the system. This is an information disclosure vulnerability requiring local access.

MitigationApply the vendor-supplied patches: macOS Big Sur 11.0.1 or later, iOS/iPadOS 14.2 or later, watchOS 7.1 or later, tvOS 14.2 or later, iCloud for Windows 11.5 or later, or iTunes 12.11 for Windows or later. Prioritize systems with sensitive data or multi-user environments.

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.5
ItunesApplication
Affected:< 12.11
IpadosOperating system
Affected:< 14.2
Iphone OsOperating system
Affected:< 14.2
Mac Os XOperating system
Affected:< 11.0.1>= 10.14, < 10.14.6>= 10.15, < 10.15.7= 10.14.6= 10.15.7
TvosOperating system
Affected:< 14.2
WatchosOperating system
Affected:< 7.1

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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 product
    Determine which Apple software is installed: on macOS, check System Preferences for iCloud; on Windows, open Control Panel > Programs and Features to find iCloud or iTunes; on iOS/tvOS/watchOS, check Settings > General > About
    Affected if Any of these Apple products are installed: iCloud for Windows, iTunes for Windows, iPadOS, iOS, macOS, tvOS, or watchOS
  2. Check iCloud for Windows version
    Open Windows Control Panel > Programs and Features, locate Apple iCloud, and note the version number displayed
    Affected if Version is earlier than 11.5
  3. Check iTunes for Windows version
    Open Windows Control Panel > Programs and Features, locate iTunes, and note the version number displayed; alternatively, open iTunes and go to Help > About iTunes
    Affected if Version is earlier than 12.11
  4. Check macOS version
    Click Apple menu > About This Mac to display the macOS version number
    Affected if Version is 10.14.6, 10.14.x before 10.14.6, 10.15.x before 10.15.7, or any version earlier than 11.0.1 (including 10.14 and earlier)
  5. Check iOS/iPadOS version
    Open Settings app, go to General > About, and note the version number displayed
    Affected if Version is earlier than 14.2
  6. Check tvOS or watchOS version
    Open Settings app on the Apple TV or Apple Watch companion iPhone app, go to General > About, and note the version number
    Affected if tvOS version is earlier than 14.2 or watchOS version is earlier than 7.1

You are affected if any of the identified Apple products have versions below the fixed releases (iCloud < 11.5, iTunes < 12.11, iOS/iPadOS < 14.2, macOS < 11.0.1 with the 10.14.6/10.15.7 caveat, tvOS < 14.2, watchOS < 7.1) and are accessible to local authenticated users.

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.1 / 10.14.6 / 10.15.7 or later
Fixed in 7.110.14.610.15.7
Interim mitigation

Apply the vendor-supplied patches: macOS Big Sur 11.0.1 or later, iOS/iPadOS 14.2 or later, watchOS 7.1 or later, tvOS 14.2 or later, iCloud for Windows 11.5 or later, or iTunes 12.11 for Windows or later. Prioritize systems with sensitive data or multi-user environments.

Fix this in Icloud Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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