dbcve.org
SafariWeb browser · Apple

CVE-2019-8816

HIGH · 8.8 CVSS v3.1 Published 2019-12-18
Fix available
A fix is available. Upgrade to 7.15 / 12.10.2 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
Multiple memory corruption issues were addressed with improved memory handling. This issue is fixed in iOS 13.2 and iPadOS 13.2, tvOS 13.2, watchOS 6.1, Safari 13.0.3, iTunes for Windows 12.10.2, iCloud for Windows 11.0, iCloud for Windows 7.15. 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 · moderate confidence

Memory corruption vulnerability in WebKit affecting Safari and system browsers on Apple devices. Processing maliciously crafted web content allows attackers to achieve arbitrary code execution through heap corruption, likely use-after-free or similar memory management flaw.

MitigationApply vendor-supplied updates: iOS 13.2/iPadOS 13.2, tvOS 13.2, watchOS 6.1, Safari 13.0.3, iTunes 12.10.2, iCloud for Windows 11.0/7.15. Deploy via MDM or software distribution tools and verify installation.

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:< 13.0.3
Enterprise Linux DesktopOperating system
Affected:= 7.0
Enterprise Linux ServerOperating system
Affected:= 7.0
Enterprise Linux WorkstationOperating system
Affected:= 7.0
IcloudApplication
Affected:< 7.15>= 10.0, <= 10.4
ItunesApplication
Affected:< 12.10.2
IpadosOperating system
Affected:< 13.2
Iphone OsOperating system
Affected:< 13.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 iOS version on iPhone
    Go to Settings > General > About on the device and look at the Version field
    Affected if The version number is less than 13.2 (for example, 13.1.3 or earlier)
  2. Check iPadOS version on iPad
    Go to Settings > General > About on the device and look at the Version field
    Affected if The version number is less than 13.2 (for example, 13.1 or earlier)
  3. Check Safari version on macOS
    Open Safari and go to Safari > About Safari (or press Cmd+, and click Safari in the sidebar)
    Affected if The version shown is earlier than 13.0.3 (such as 13.0.2, 13.0.1, or 13.0)
  4. Check iTunes version on Windows or macOS
    Open iTunes and go to Help > About iTunes
    Affected if The version shown is earlier than 12.10.2 (such as 12.10.1 or 12.10)
  5. Check iCloud for Windows version
    Open the iCloud desktop app and navigate to its version information, typically via the app menu or About section
    Affected if The version is 10.0 through 10.4, or is earlier than 7.15 (compare your installed version to these affected ranges)
  6. Check WebKit package on RHEL 7
    Run 'rpm -qa | grep -i webkit' or 'yum list installed webkit' to list installed WebKit-related packages, then query the specific package version with 'rpm -q <package-name>'
    Affected if WebKit packages are installed on RHEL 7.0 Desktop, Server, or Workstation (compare your installed version to determine if unpatched)

A user is affected if any of their Apple device operating systems (iOS, iPadOS), Apple software (Safari, iTunes, iCloud for Windows), or RHEL 7 WebKit installations match the vulnerable versions listed.

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.15 / 12.10.2 / 13.0.3 or later
Fixed in 7.1512.10.213.0.3
Interim mitigation

Apply vendor-supplied updates: iOS 13.2/iPadOS 13.2, tvOS 13.2, watchOS 6.1, Safari 13.0.3, iTunes 12.10.2, iCloud for Windows 11.0/7.15. Deploy via MDM or software distribution tools and verify installation.

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-8816 — 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-8816 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