dbcve.org
SafariWeb browser · Apple

CVE-2019-8583

HIGH · 8.8 CVSS v3.1 Published 2019-12-18
Fix available
A fix is available. Upgrade to 5.2.1 / 7.12 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 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 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 that allows arbitrary code execution when processing maliciously crafted web content. Affects Safari and web rendering components in iOS, macOS, tvOS, watchOS, iTunes, and iCloud for Windows.

MitigationApply vendor-supplied patches by updating to iOS 12.3+, macOS Mojave 10.14.5+, tvOS 12.3+, watchOS 5.2.1+, Safari 12.1.1+, iTunes 12.9.5+, or iCloud for Windows 7.12+ as appropriate for each affected system.

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
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 iOS, go to Settings > Safari > About. Note the version number displayed.
    Affected if Version is earlier than 12.1.1 and Safari is used to browse web content
  2. Check iTunes version
    Open iTunes on Windows or macOS, then go to Help > About iTunes. Note the version number shown in the dialog.
    Affected if Version is earlier than 12.9.5 and iTunes is used to process web content or access the iTunes Store
  3. Check iCloud for Windows version
    Open iCloud on Windows, click the gear icon or go to Help > About iCloud. Note the version number displayed.
    Affected if Version is earlier than 7.12 or falls between 10.0 and 10.4, and iCloud is used for web content sync or browsing
  4. Check macOS version
    Click Apple menu > About This Mac. Note the version number under macOS.
    Affected if Version is earlier than 10.14.5 (Mojave) and Safari or other WebKit-based apps are used for web browsing
  5. Check iOS version
    On iPhone or iPad, go to Settings > General > About. Note the iOS version number.
    Affected if Version is earlier than 12.3 and Safari or any app using WebKit is used to view web content
  6. Check tvOS or watchOS version
    On Apple TV, go to Settings > General > About. On Apple Watch, open the Watch app on iPhone and go to General > About.
    Affected if tvOS is earlier than 12.3 or watchOS is earlier than 5.2.1, and the built-in browser is used

You are affected if any installed Apple product (Safari, iTunes, iCloud, iOS, macOS, tvOS, or watchOS) has a version below its fixed version AND you use that product to process or view web content.

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 by updating to iOS 12.3+, macOS Mojave 10.14.5+, tvOS 12.3+, watchOS 5.2.1+, Safari 12.1.1+, iTunes 12.9.5+, or iCloud for Windows 7.12+ as appropriate for each affected system.

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