dbcve.org
SafariWeb browser · Apple

CVE-2019-8570

MEDIUM · 6.5 CVSS v3.1 Published 2020-10-27
Fix available
A fix is available. Upgrade to 7.10 / 12.0.3 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable 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 logic issue was addressed with improved state management. This issue is fixed in iOS 12.1.3, iCloud for Windows 7.10, iTunes 12.9.3 for Windows, Safari 12.0.3, tvOS 12.1.2. Processing maliciously crafted web content may disclose sensitive user information.

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

A logic vulnerability in WebKit (Apple's browser engine) allowed processing of maliciously crafted web content to potentially disclose sensitive user information due to improper state management. The vulnerability affected Safari, iOS, tvOS, and iTunes/iCloud for Windows.

MitigationApply the vendor-supplied patches: update to iOS 12.1.3 or later, Safari 12.0.3 or later, tvOS 12.1.2 or later, iCloud for Windows 7.10 or later, or iTunes 12.9.3 or later.

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
SafariWeb browser
Affected:< 12.0.3
IcloudApplication
Affected:< 7.10
ItunesApplication
Affected:< 12.9.3
Iphone OsOperating system
Affected:< 12.1.3
TvosOperating system
Affected:< 12.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
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 which Apple product uses WebKit
    Determine if Safari (macOS), iTunes (Windows), iCloud for Windows, iOS device, or Apple TV (tvOS) is in use on the system
    Affected if Any WebKit-based Apple application is present on the system
  2. Check Safari version on macOS
    Open Safari, click Safari menu, select About Safari. Compare the version number to 12.0.3
    Affected if Safari version is below 12.0.3 (for example, 12.0.2 or earlier)
  3. Check iTunes version on Windows
    Open iTunes, go to Help > About iTunes. Alternatively, open Programs and Features in Control Panel and locate iTunes in the installed programs list
    Affected if iTunes version is below 12.9.3 (for example, 12.9.2 or earlier)
  4. Check iCloud for Windows version
    Open iCloud from the system tray or Start menu, go to About. Alternatively, open Programs and Features in Control Panel and locate iCloud
    Affected if iCloud for Windows version is below 7.10 (for example, 7.9 or earlier)
  5. Check iOS version on iPhone or iPad
    Open Settings app, go to General > About, note the Version number (for example, 12.1.2)
    Affected if iOS version is below 12.1.3 (for example, 12.1.2 or earlier)
  6. Check tvOS version on Apple TV
    Open Settings app on Apple TV, go to General > About, note the version number
    Affected if tvOS version is below 12.1.2 (for example, 12.1.1 or earlier)

The system is affected if any installed Apple product (Safari, iTunes, iCloud for Windows, iOS, or tvOS) has a version lower than the fixed release (Safari 12.0.3, iTunes 12.9.3, iCloud 7.10, iOS 12.1.3, tvOS 12.1.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.10 / 12.0.3 / 12.1.2 or later
Fixed in 7.1012.0.312.1.2
Interim mitigation

Apply the vendor-supplied patches: update to iOS 12.1.3 or later, Safari 12.0.3 or later, tvOS 12.1.2 or later, iCloud for Windows 7.10 or later, or iTunes 12.9.3 or later.

Fix this in Safari 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-2019-8570 — 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-2019-8570 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