dbcve.org
SafariWeb browser · Apple

CVE-2019-8607

MEDIUM · 6.5 CVSS v3.1 Published 2019-12-18
Fix available
A fix is available. Upgrade to 5.2.1 / 7.12 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
An out-of-bounds read was addressed with improved input validation. This issue is fixed in iOS 12.3, macOS Mojave 10.14.5, tvOS 12.3, watchOS 5.2.1, Safari 12.1.1, iTunes for Windows 12.9.5, iCloud for Windows 7.12. Processing maliciously crafted web content may result in the disclosure of process memory.

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

An out-of-bounds read vulnerability in WebKit affects iOS, macOS, tvOS, watchOS, Safari, iTunes, and iCloud for Windows. The flaw stems from insufficient input validation when processing maliciously crafted web content, allowing attackers to read process memory beyond allocated buffers.

MitigationApply vendor-supplied patches (iOS 12.3+, macOS 10.14.5+, Safari 12.1.1+, etc.) to all affected systems. Until patched, restrict user access to untrusted web content and enable browser security features.

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.1
IcloudApplication
Affected:< 7.12>= 10.0, < 10.4
ItunesApplication
Affected:< 12.9.5
Iphone OsOperating system
Affected:< 12.3
Mac Os XOperating system
Affected:< 10.14.5
TvosOperating system
Affected:< 12.3
WatchosOperating system
Affected:< 5.2.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
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 installed Apple applications
    Check if any of these applications are installed: Safari, iTunes, iCloud for Windows. On macOS, open Finder > Applications. On Windows, check Program Files or via Control Panel > Programs and Features.
    Affected if Any of these applications are installed and the version falls within the affected ranges below.
  2. Check Safari version
    Open Safari > About Safari (or Safari menu > About Safari on Windows). Compare the version number to 12.1.1.
    Affected if Version is earlier than 12.1.1.
  3. Check iTunes version
    Open iTunes > Help > About iTunes. Compare the version number to 12.9.5.
    Affected if Version is earlier than 12.9.5.
  4. Check iCloud for Windows version
    Open iCloud > About iCloud. Compare the version number to the affected ranges: versions earlier than 7.12, or versions 10.0 through 10.4.
    Affected if Version is less than 7.12, or between 10.0 and 10.4 inclusive.
  5. Check macOS version
    Click Apple menu > About This Mac. Compare the OS version to 10.14.5.
    Affected if OS version is earlier than 10.14.5.
  6. Check iOS, tvOS, or watchOS version
    On iOS: Settings > General > About > Version. On tvOS: Settings > General > About > Version. On watchOS: On iPhone, open Watch app > My Watch > General > About. Compare to affected versions (iOS < 12.3, tvOS < 12.3, watchOS < 5.2.1).
    Affected if The device OS version is earlier than the fixed version for that platform.

A system is affected if it runs any of the listed products (Safari, iTunes, iCloud for Windows, iOS, macOS, tvOS, or watchOS) with a version number below the corresponding threshold specified in the affected version ranges.

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 5.2.1 / 7.12 / 10.4 or later
Fixed in 5.2.17.1210.4
Interim mitigation

Apply vendor-supplied patches (iOS 12.3+, macOS 10.14.5+, Safari 12.1.1+, etc.) to all affected systems. Until patched, restrict user access to untrusted web content and enable browser security features.

Fix this in Safari Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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