dbcve.org
SafariWeb browser · Apple

CVE-2019-8536

HIGH · 8.8 CVSS v3.1 Published 2019-12-18
Fix available
A fix is available. Upgrade to 7.11 / 12.1 or later.
See remediation →
95/100
Remediation priority · Urgent
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 memory corruption issue was addressed with improved memory handling. This issue is fixed in iOS 12.2, tvOS 12.2, watchOS 5.2, Safari 12.1, iTunes 12.9.4 for Windows, iCloud for Windows 7.11. Processing maliciously crafted web content 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

Memory corruption vulnerability in WebKit (Apple's browser engine) that allows arbitrary code execution when processing maliciously crafted web content. Affects iOS, tvOS, watchOS, Safari, iTunes, and iCloud for Windows.

MitigationApply vendor-supplied patches by updating all affected Apple products to the fixed versions: iOS 12.2+, tvOS 12.2+, watchOS 5.2+, Safari 12.1+, iTunes 12.9.4+, and iCloud for Windows 7.11+.

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.1
Enterprise Linux DesktopOperating system
Affected:= 7.0
Enterprise Linux ServerOperating system
Affected:= 7.0
Enterprise Linux WorkstationOperating system
Affected:= 7.0
IcloudApplication
Affected:< 7.11
ItunesApplication
Affected:< 12.9.4
Iphone OsOperating system
Affected:< 12.2
TvosOperating system
Affected:< 12.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
High
Availability
High

CVSS:3.1/AV:N/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. Check Safari version
    On macOS, open Safari and go to Safari > About Safari. On Windows, open iTunes and check Safari version under Help > About Safari, or check the installed Safari version in Programs and Features.
    Affected if Version is below 12.1 (for example, 12.0.x or earlier)
  2. Check iOS version
    On the iOS device, go to Settings > General > About > Version. Alternatively, connect the device to Finder (macOS) or iTunes (Windows) and check the device summary page.
    Affected if Version is below 12.2 (for example, 12.1.x or earlier)
  3. Check tvOS version
    On Apple TV, go to Settings > General > About > Version. Alternatively, check in Finder or iTunes when the device is connected.
    Affected if Version is below 12.2 (for example, 12.1.x or earlier)
  4. Check iTunes version
    Open iTunes on Windows or macOS and go to Help > About iTunes. On Windows, also check Programs and Features.
    Affected if Version is below 12.9.4 (for example, 12.9.3 or earlier)
  5. Check iCloud for Windows version
    Open iCloud for Windows and click the gear icon or menu to access About or version information. On Windows, also check Programs and Features.
    Affected if Version is below 7.11 (for example, 7.10 or earlier)
  6. Check WebKit on RHEL 7.0
    Run 'rpm -qa | grep -i webkit' to list installed WebKit packages. Check specific packages like webkit2gtk or webkitgtk using 'rpm -q <package-name>' to get exact versions.
    Affected if WebKit packages are installed on RHEL 7.0 (exact version matching the 7.0 release build)

You are affected if any of your installed product versions fall within the vulnerable ranges: Safari < 12.1, iOS < 12.2, tvOS < 12.2, iTunes < 12.9.4, iCloud for Windows < 7.11, or WebKit on RHEL 7.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 7.11 / 12.1 / 12.2 or later
Fixed in 7.1112.112.2
Interim mitigation

Apply vendor-supplied patches by updating all affected Apple products to the fixed versions: iOS 12.2+, tvOS 12.2+, watchOS 5.2+, Safari 12.1+, iTunes 12.9.4+, and iCloud for Windows 7.11+.

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