IcloudApplication · Apple

CVE-2019-8750

CRITICAL · 9.8 CVSS v3.1 Published 2019-12-18
Fix available
A fix is available. Upgrade to 6.1 / 10.8 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Multiple memory corruption issues were addressed with improved input validation. This issue is fixed in watchOS 6.1, iCloud for Windows 11.0. Multiple issues in libxslt.

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 · moderate confidence

Memory corruption vulnerability in libxslt library caused by insufficient input validation when processing XML/XSLT documents. This can lead to arbitrary code execution or denial of service. Fixed in watchOS 6.1 and iCloud for Windows 11.0.

MitigationUpdate affected Apple products (watchOS 6.1+, iCloud for Windows 11.0+) or patch libxslt library in third-party applications to address the memory corruption issues.

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:< 10.8
WatchosOperating system
Affected:< 6.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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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. Check if iCloud for Windows is installed
    Open Windows Control Panel > Programs and Features, or check C:\Program Files\Apple Software Update\iCloud.exe exists, or search for 'iCloud' in the Start menu
    Affected if iCloud for Windows is installed and version is below 10.8
  2. Determine installed iCloud for Windows version
    Right-click iCloud in the Start menu, select 'Open file location', right-click the iCloud executable, select Properties, and check the 'Details' tab for Product version
    Affected if Version shown is less than 10.8 (for example, 10.7.x or earlier)
  3. Check Apple Watch paired with iPhone
    Open the Watch app on paired iPhone, go to General > About, or check the Apple Watch directly by opening Settings > General > About on the watch
    Affected if watchOS version displayed is below 6.1 (for example, 6.0.x or earlier)
  4. Verify libxslt usage in third-party applications
    If using third-party software that processes XML/XSLT documents, check the application's 'About' or 'Help' dialog to identify the bundled libxslt version, or examine the application's installation folder for libxslt.dll
    Affected if Application bundles a version of libxslt prior to the patched release used in Apple's fix

User is affected if they have iCloud for Windows installed with version below 10.8, or an Apple Watch running watchOS below 6.1, or third-party apps using a vulnerable libxslt version.

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.

dbcve · scoped
Upgrade available Upgrade to 6.1 / 10.8 or later
Fixed in 6.110.8
Interim mitigation

Update affected Apple products (watchOS 6.1+, iCloud for Windows 11.0+) or patch libxslt library in third-party applications to address the memory corruption issues.

Recommended fix High confidence

iCloud for Windows 11.0; watchOS 6.1

  1. For iCloud for Windows: Download and install iCloud for Windows version 11.0 from the official Apple website or Microsoft Store
  2. For Apple Watch: Connect your Apple Watch to power, then open the Watch app on your paired iPhone and navigate to General > Software Update to install watchOS 6.1
  3. After updating, verify the installed versions: iCloud for Windows should show version 11.0, and Apple Watch should show watchOS 6.1
Caveat Users should ensure they have compatible devices and backup data before updating; watchOS 6.1 requires iPhone with iOS 13 or later

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Icloud Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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